Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.19
-
None
-
centos 7
Description
I just upgraded to 10.1.19 and recompiled the Java code for the JdbcInterface and ApacheInterface. The null behavior is different than 10.1.18 but still not correct.
In 10.1.19 when you INSERT a row with NULL values specified for numeric or date/time column datatypes (all of their various forms) and then SELECT the result back, you will see that 0 was INSERTed.
Note however that now in 10.1.19 if you issue an UPDATE statement with null values the behavior is now correct (when you select back you get NULLs for numbers and dates).