mirror of
https://github.com/django/django.git
synced 2025-10-31 09:41:08 +00:00
Consolidated documentation for F() and Q()
This commit is contained in:
@@ -679,13 +679,14 @@ Miscellaneous
|
||||
needs. The new default value is ``0666`` (octal) and the current umask value
|
||||
is first masked out.
|
||||
|
||||
* The :ref:`F() expressions <query-expressions>` supported bitwise operators by
|
||||
* The :class:`F expressions <django.db.models.F>` supported bitwise operators by
|
||||
``&`` and ``|``. These operators are now available using ``.bitand()`` and
|
||||
``.bitor()`` instead. The removal of ``&`` and ``|`` was done to be consistent with
|
||||
:ref:`Q() expressions <complex-lookups-with-q>` and ``QuerySet`` combining where
|
||||
the operators are used as boolean AND and OR operators.
|
||||
``.bitor()`` instead. The removal of ``&`` and ``|`` was done to be
|
||||
consistent with :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>`
|
||||
* In a ``filter()`` call, when :class:`F expressions <django.db.models.F>`
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user