#18375: F() doesn't work as expected across multijoin relations
-------------------------------------+-------------------------------------
Reporter: FunkyBob | Owner: akaariai
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by nicolas):
I think the documentation for this is overly complicated and requires
detailed knowledge of what the SQL translation will be (which the ORM
users shouldn't need).
The fix to only use one reference would probably work for 90% of the cases
and for the other cases where you need to control exactly how the SQL
query would be written you can fallback to raw SQL. I don't see a need for
DupeMultisF; this fine grained control belongs in the SQL layer and not
the ORM layer. Documenting that this generates a single join in 1.5 should
be enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/18375#comment:12>
Django <https://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 https://groups.google.com/groups/opt_out.
