Russell Keith-Magee: > Sorry - I'm confused; Are you agreeing with the proposed change, or > saying it contradicts your expectations? (I think you are agreeing - I > just want to make sure)
My highest preference is to make __exact=None behave like WHERE xxx=NULL, i.e. returning an empty set, against current behaviour *and* against your proposal. My middle preference is what you propose: making __exact=None a replacement for __isnull=True. My lowest preference is to keep it as it is: ignore __exact=None Please, excuse me for being so complicated today ;-) 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 -~----------~----~----~----~------~----~------~--~---
