#9981: getting objects where column is null throws exception, when you define
ordering by that column
-----------------------------------------------------+----------------------
Reporter: [email protected] | Owner:
mtredinnick
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: worksforme | Keywords: foreign
keys, null, get
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------+----------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => worksforme
Comment:
I tested the example provided in the description with SQLite, PostgreSQL
and MySQL using both current subversion trunk and the Django 1.0.X branch.
Could not repeat the problem.
If the original reporter has more details about how to recreate this issue
reliably with either trunk HEAD or Django 1.0.2, please reopen with
details. We would need to know at least the database being used and what
the definition of Bar is. However, I cannot see from the code how this
result would be possible as a rule. It's not impossible to replicate if,
say, some other thread of execution deleted the object between the
creation and the `get()` call and the database wasn't using transactions
(MYSQL with MyIsam, perhaps), but that's not a bug in Django.
For now, closing as worksforme.
--
Ticket URL: <http://code.djangoproject.com/ticket/9981#comment:4>
Django <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
-~----------~----~----~----~------~----~------~--~---
