#7270: selected_related() can not follow reverse relations of OneToOne.
---------------------------------------------------+------------------------
Reporter: towjz...@hotmail.com | Owner:
mtredinnick
Status: new | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
select_related onetoone reverse
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by dchristian):
We have a generic Content type, and a Article type that is a more specific
type of content. Content is linked to by other sub-objects, one of which
is a OneToOne but is kept in a different app to keep things separated
nicely.
But in any case, the point is that this patch, if applied, will result in
tracebacks when used in that situation, so I wouldn't recommend approving
it until the situation is at least handled in some way that doesn't crash.
--
Ticket URL: <http://code.djangoproject.com/ticket/7270#comment:54>
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
-~----------~----~----~----~------~----~------~--~---
