All,
First, a HUGE thank you to all who participated in the discussion. It
was, as is usually the case in an open, transparent forum, very
enlightening.
It was clear after reading all the discussion:
a) that the SQL standard is indeed clear in the area
b) that Drizzle should throw an error when a NULL value is inserted
manually into a NOT NULL column (with 2 notable exceptions, see below)
c) that there is a possible bug in LOAD DATA INFILE in both MySQL and
Drizzle which, even in sql_mode=strict_xxx (MySQL) LOAD DATA INFILE does
not throw an error
Therefore, going forward, I will ensure our null-behaviour test case
tests for appropriate error throwing in all cases, including LOAD DATA
INFILE and multi-row INSERTs.
BTW, the two exceptions to the rule are:
1) AUTOINCREMENT fields, where inserting a NULL will insert the next
autoincrement value
2) For TIMESTAMP fields, where inserting a NULL inserts the current
timestamp
Cheers, and thanks all for your help!
Jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
