#2737: DB API and Model Interface don't agree on meaning of None
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: Database wrapper
Version: SVN | Resolution: wontfix
Keywords: exclude filter None | Stage: Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------------+------------------------------------
Changes (by mtredinnick):
* status: reopened => closed
* resolution: => wontfix
Comment:
The current behaviour is intentional and the behaviour is documented.
See [http://groups.google.com/group/django-
developers/browse_thread/thread/e36e80faf653b6d4/934debbe1a59ee1a?lnk=gst&q=queries+%22%3D+None%22&rnum=1#
this thread] for the justification. It's a weird corner-case, but doing an
exact match against NULL won't give sensible results in any case, as
mentioned in the above thread.
--
Ticket URL: <http://code.djangoproject.com/ticket/2737#comment:7>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
