On 12 Sep 2008, at 05:45, Jay Pipes wrote:
OK, thank you to all who provided input, especially to Arjen and
Roland
who made this confusing SQL mode a lot easier to understand. Granted,
as Arjen pointed out, I had confused the HIGH_NOT_PRECEDENCE sql
mode as
being something *that was added to provide SQL compatibility*. Turns
out, as Arjen says, it was added to provide *backwards compatibility*
with the old, incorrect pre MySQL 4.1 behaviour.
Yes, the HIGH_NOT_PRECEDENCE mode is for backwards compatibility.
I originally wanted to call it something like BACKWARDS_COMPAT_NOT but
after a short discussion with PeterG, we opted for the name you see.
<snip>
Regards,
Antony.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
