On Tue, 2009-03-24 at 16:50 -0400, Michael Glassford wrote: > Alex Gaynor wrote: > > > > I'm almost positive the MySQL CLI operates differently for the purposes > > of this query. The reason the queries do different things in .96 is > > that in .96 that query becomes id = NULL rather than id IS NULL, which > > MySQL handles differently. > > > > Well, that fits the facts that I know. However, from a Django point of > view it's pretty unexpected. Would you agree that it should be > considered a Django bug, and should be fixed?
It's not a bug. You are receiving exactly what the database offers up for that query. Yes, the behaviour would be considered a show-stopping bug for any normal database. MySQL considers it a feature. We're not going to interfere with that, since (a) people are free to choose their own database server and (b) some people might actually agree with the MySQL developers and be relying on that behaviour. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
