Hi! On Tue, Dec 16, 2008 at 11:56 PM, Arjen Lentz <[email protected]> wrote: >> Ostensibly, the above behaviour was designed so that LOAD DATA and other >> multi-row or batch operations would continue if a NULL value was inserted >> into a NOT NULL column. > > I think this is the key issue, this behaviour was designed to deal with a > non-transactional environment. > Since Drizzle is getting rid of that architecture, the reason-to-be for this > behaviour has disappeared also.
I fail to see how this has got anything at all to do with transactions. I mean, NOT NULL is a constraint - no more, no less. LOAD DATA INFILE does fail on a UNIQUE constraint, possibly aborting the remainder of the work. Why should a NOT NULL constraint be treated differently? > Yes. Rationale: if a column was defined as NOT NULL, then NULL is not valid. > Magically changing it into some value (whatever it may be) is not good; > MySQL did just it by necessity because of MyISAM being non-transactional. I'm still not convinced this is relevant to this matter ;-) Regards, Roland > > > Cheers, > Arjen. > -- > Arjen Lentz, Director @ Open Query (http://openquery.com.au) > Training and Expertise for MySQL and related tools > > OurDelta: free enhanced builds for MySQL @ http://ourdelta.org > > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > -- Roland Bouman http://rpbouman.blogspot.com/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
