Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 2a2708e1b2a0e02fc4fdd4b050d60fb0033dfdde
https://github.com/django/django/commit/2a2708e1b2a0e02fc4fdd4b050d60fb0033dfdde
Author: Anssi Kääriäinen <[email protected]>
Date: 2013-03-15 (Fri, 15 Mar 2013)
Changed paths:
M tests/model_inheritance_regress/tests.py
Log Message:
-----------
Fixed #17502 -- Made joining in inheritance cases consistent
The original problem was that when filtering two levels up in
inheritance chain, Django optimized the join generation so that the
middle model was skipped. But then Django generated joins from top
to middle to bottom for SELECT clause, and thus there was one extra
join (top->middle->bottom + top -> bottom).
This case is fixed in master as the filtering optimization is gone.
This has the side effect that in some cases there is still extra join
if the SELECT clause doesn't contain anything from middle or bottom.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
