diff options
| author | Tim Graham <timograham@gmail.com> | 2012-12-29 10:35:12 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-12-29 15:57:57 -0500 |
| commit | 9e5ada79bf2d25fa862babe74517a6c7b5b89968 (patch) | |
| tree | 78937f2f77f75a4279cce7440c50186d74297658 /docs/topics/db | |
| parent | d529d413f742b16e787c5ddb4e843fa66d1b0809 (diff) | |
[1.5.x] Fixed broken links, round 4. refs #19516
Backport of 067505ad19 from master
Diffstat (limited to 'docs/topics/db')
| -rw-r--r-- | docs/topics/db/queries.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index a869b6afad..046c23bdcd 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -601,6 +601,8 @@ relation may end up filtering on different linked objects. Filters can reference fields on the model ----------------------------------------- +.. class:: F + In the examples given so far, we have constructed filters that compare the value of a model field with a constant. But what if you want to compare the value of a model field with another field on the same model? @@ -755,6 +757,8 @@ To avoid this problem, simply save the Complex lookups with Q objects ============================== +.. class:: Q + Keyword argument queries -- in :meth:`~django.db.models.query.QuerySet.filter`, etc. -- are "AND"ed together. If you need to execute more complex queries (for example, queries with ``OR`` statements), you can use ``Q`` objects. |