Russell Keith-Magee schrieb: > Ticket 2737 requests a feature where __exact=None would be interpreted > as __isnull=True. This would fix all three problems I have described. > The proposed patch isn't correct, but I feel the idea is valid.
My brain has been wired in SQL mode, perhaps for too long, so I consider __exact=None as the equivalent of ... WHERE ...=NULL, which gives an empty result set. Perhaps this comes to a surprise for an SQL newbie, but it is seriously my intuitive expectation, being consistent with the SQL boolean algebra. Well. If it's only me, ignore me, it would still be an improvement above the current situation, and I probably can get over it ;-) Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
