On Thu, 2006-10-12 at 11:43 +0800, Russell Keith-Magee wrote: [...] > Also, fixing this problem is problematic because it encroaches upon > Malcolm's refactor of the QuerySet code. > > Comments? Have I missed an obvious problem? Have I missed a ticket in > the database that describes this problem already? Malcolm, can you > comment on the potential impact a short term fix for this problem > would have on your refactor work?
Ignore the impact on my stuff. I'll catch up with that change. I agree the second two cases are bugs. I'm probably -0 on making exact=None be the same as isnull=True, because it's a synonym for something you can already do (we already have isnull). Still, I guess it's a harmless change (which is why I'm not -1). Regards, Malcolm > > Yours, > Russ Magee %-) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
