#7512: including a nullable foreign key reference in Meta ordering has
unexpected
results
----------------------------------------------------+-----------------------
Reporter: R. Bailey <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: assigned | Milestone: 1.0
Component: Database wrapper | Version: SVN
Resolution: | Keywords:
1.0-blocker
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
----------------------------------------------------+-----------------------
Comment (by mtredinnick):
So once I started looking at this, it was looking familiar. Then I
realised I had mostly fixed it in r7761 (see #7181). I just missed one
portion that George's test here shows up: chained models with a nullable
join leading to a non-nullable join. So I've added the test (thanks!) and
the two line fix.
--
Ticket URL: <http://code.djangoproject.com/ticket/7512#comment:11>
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
-~----------~----~----~----~------~----~------~--~---
