test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Removed suggestion of temporary lookup registration from docs

This commit is contained in:
Anssi Kääriäinen 2014-01-12 19:51:53 +02:00
parent 21d0c7631c
commit 3b18d9f3a1
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ref/models/custom_lookups.txt
View File

@ -216,12 +216,6 @@ When compiling a query, Django first looks for ``as_%s % connection.vendor``
methods, and then falls back to ``as_sql``. The vendor names for the in-built methods, and then falls back to ``as_sql``. The vendor names for the in-built
backends are ``sqlite``, ``postgresql``, ``oracle`` and ``mysql``. backends are ``sqlite``, ``postgresql``, ``oracle`` and ``mysql``.
.. note::
If for some reason you need to change the lookup just for a specific query,
you can do that and reregister the original lookup afterwards. However you
need to be careful to ensure that your patch is in place until the queryset
is evaluated, not just created.
.. _query-expression: .. _query-expression:
The Query Expression API The Query Expression API