Hi!
On Aug 13, 2008, at 4:00 PM, Brian Moon wrote:
So, in non-strict mode (drizzle gonna have more than one mode?), we
get a field inserted with an empty value. Not the default
value?!?! IMO, it should either fail on insert/update or should use
the default value. Using a value that is not part of the allowed
values seems crazy to me.
I believe that I fixed this early on, but I could be wrong.
In drizzle if you insert/update an enum which is not null, a failure
should occur (and if not, it is a bug).
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
