diff options
| author | Sébastien Fievet <zyegfryed@gmail.com> | 2014-09-07 11:29:20 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-09-07 06:29:52 -0400 |
| commit | 267b121b1e8a87adc61771ec786e6d9037df2462 (patch) | |
| tree | cdbf226447d656ca7dba8c4e1c18577a82c414fb | |
| parent | 48e10710074a06584b6f8331a6e74492be5acf18 (diff) | |
[1.7.x] Fixed typo in docs/howto/custom-lookups.txt.
Backport of f36ab2d3f2 from master
| -rw-r--r-- | docs/howto/custom-lookups.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/howto/custom-lookups.txt b/docs/howto/custom-lookups.txt index af7c18e38c..c02b896071 100644 --- a/docs/howto/custom-lookups.txt +++ b/docs/howto/custom-lookups.txt @@ -226,7 +226,7 @@ backends are ``sqlite``, ``postgresql``, ``oracle`` and ``mysql``. How Django determines the lookups and transforms which are used ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -In some cases you may which to dynamically change which ``Transform`` or +In some cases you may wish to dynamically change which ``Transform`` or ``Lookup`` is returned based on the name passed in, rather than fixing it. As an example, you could have a field which stores coordinates or an arbitrary dimension, and wish to allow a syntax like ``.filter(coords__x7=4)`` to return |