#9981: getting objects where column is null throws exception, when you define ordering by that column -----------------------------------------------------+---------------------- Reporter: antje.ga...@taconicartemis.com | Owner: nobody Status: reopened | Milestone: Component: Database layer (models, ORM) | Version: SVN Resolution: | Keywords: foreign keys, null, get Stage: Unreviewed | Has_patch: 0 Needs_docs: 0 | Needs_tests: 0 Needs_better_patch: 0 | -----------------------------------------------------+---------------------- Changes (by mtredinnick):
* status: closed => reopened * resolution: invalid => Comment: Reopening until I check what the behaviour is here. This shouldn't be happening; if it is, some database server is broken. In that case, we should work around it. -- Ticket URL: <http://code.djangoproject.com/ticket/9981#comment:2> 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 django-updates@googlegroups.com To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---