mirror of
https://github.com/django/django.git
synced 2025-10-23 21:59:11 +00:00
Refs #36485 -- Rewrapped docs to 79 columns line length.
Lines in the docs files were manually adjusted to conform to the 79 columns limit per line (plus newline), improving readability and consistency across the content.
This commit is contained in:
@@ -11,8 +11,8 @@ Indexing these fields
|
||||
=====================
|
||||
|
||||
:class:`~django.db.models.Index` and :attr:`.Field.db_index` both create a
|
||||
B-tree index, which isn't particularly helpful when querying complex data types.
|
||||
Indexes such as :class:`~django.contrib.postgres.indexes.GinIndex` and
|
||||
B-tree index, which isn't particularly helpful when querying complex data
|
||||
types. Indexes such as :class:`~django.contrib.postgres.indexes.GinIndex` and
|
||||
:class:`~django.contrib.postgres.indexes.GistIndex` are better suited, though
|
||||
the index choice is dependent on the queries that you're using. Generally, GiST
|
||||
may be a good choice for the :ref:`range fields <range-fields>` and
|
||||
@@ -450,8 +450,8 @@ operator ``?|``. For example:
|
||||
``has_keys``
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Returns objects where all of the given keys are in the data. Uses the SQL operator
|
||||
``?&``. For example:
|
||||
Returns objects where all of the given keys are in the data. Uses the SQL
|
||||
operator ``?&``. For example:
|
||||
|
||||
.. code-block:: pycon
|
||||
|
||||
@@ -741,8 +741,8 @@ passed range.
|
||||
``not_gt``
|
||||
^^^^^^^^^^
|
||||
|
||||
The returned ranges do not contain any points greater than the passed range, that
|
||||
is the upper bound of the returned range is at most the upper bound of the
|
||||
The returned ranges do not contain any points greater than the passed range,
|
||||
that is the upper bound of the returned range is at most the upper bound of the
|
||||
passed range.
|
||||
|
||||
>>> Event.objects.filter(ages__not_gt=NumericRange(3, 10))
|
||||
|
||||
Reference in New Issue
Block a user