summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAnssi Kääriäinen <akaariai@gmail.com>2012-11-22 20:27:28 +0200
committerAnssi Kääriäinen <akaariai@gmail.com>2012-11-23 19:53:04 +0200
commit90b86291d022a09031d1df397d7aaebc30e435f7 (patch)
treed0264a1fee77724db1660d8ac807c4689189051d /docs
parent7b9a1fb9649d169f4ec0e539c4901c66b0f5ebb6 (diff)
Fixed #18375 -- Removed dict-ordering dependency for F-expressions
F() expressions reuse joins like any lookup in a .filter() call - reuse multijoins generated in the same .filter() call else generate new joins. Also, lookups can now reuse joins generated by F(). This change is backwards incompatible, but it is required to prevent dict randomization from generating different queries depending on .filter() kwarg ordering. The new way is also more consistent in how joins are reused.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.5.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt
index e26b927ae7..ca6b3acfd9 100644
--- a/docs/releases/1.5.txt
+++ b/docs/releases/1.5.txt
@@ -589,6 +589,12 @@ Miscellaneous
:ref:`Q() expressions <complex-lookups-with-q>` and ``QuerySet`` combining where
the operators are used as boolean AND and OR operators.
+* In a ``filter()`` call, when :ref:`F() expressions <query-expressions>`
+ contained lookups spanning multi-valued relations, they didn't always reuse
+ the same relations as other lookups along the same chain. This was changed,
+ and now F() expressions will always use the same relations as other lookups
+ within the same ``filter()`` call.
+
* The :ttag:`csrf_token` template tag is no longer enclosed in a div. If you need
HTML validation against pre-HTML5 Strict DTDs, you should add a div around it
in your pages.