diff options
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/fields.txt | 11 | ||||
| -rw-r--r-- | docs/ref/models/querysets.txt | 5 |
2 files changed, 7 insertions, 9 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 8a348f092e..21409f562b 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1847,15 +1847,8 @@ Field API reference .. method:: get_prep_lookup(lookup_type, value) Prepares ``value`` to the database prior to be used in a lookup. - The ``lookup_type`` will be one of the valid Django filter lookups: - ``"exact"``, ``"iexact"``, ``"contains"``, ``"icontains"``, - ``"gt"``, ``"gte"``, ``"lt"``, ``"lte"``, ``"in"``, ``"startswith"``, - ``"istartswith"``, ``"endswith"``, ``"iendswith"``, ``"range"``, - ``"year"``, ``"month"``, ``"day"``, ``"isnull"``, ``"search"``, - ``"regex"``, and ``"iregex"``. - - If you are using :doc:`Custom lookups </ref/models/lookups>` the - ``lookup_type`` can be any ``lookup_name`` registered in the field. + The ``lookup_type`` will be the registered name of the lookup. For + example: ``"exact"``, ``"iexact"``, or ``"contains"``. See :ref:`preparing-values-for-use-in-database-lookups` for usage. diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 8781c4cdd4..6bb8cf81ce 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -2771,6 +2771,11 @@ SQL equivalent:: ``search`` ~~~~~~~~~~ +.. deprecated:: 1.10 + + See :ref:`the 1.10 release notes <search-lookup-replacement>` for how to + replace it. + A boolean full-text search, taking advantage of full-text indexing. This is like :lookup:`contains` but is significantly faster due to full-text indexing. |