diff options
| author | Tim Graham <timograham@gmail.com> | 2018-05-17 10:16:32 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-05-17 11:00:10 -0400 |
| commit | 7543ab1f8dcb20dbbdf6a41eace95fc47c8dcaa3 (patch) | |
| tree | 98e0f0cbec43f45ea36c09cafb97385bca028a9f /docs/ref/models | |
| parent | 1cbd3d7874a4887fa2a6d7ef582defc388429b97 (diff) | |
Removed versionadded/changed annotations for 2.0.
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/database-functions.txt | 12 | ||||
| -rw-r--r-- | docs/ref/models/expressions.txt | 14 | ||||
| -rw-r--r-- | docs/ref/models/indexes.txt | 2 | ||||
| -rw-r--r-- | docs/ref/models/options.txt | 8 | ||||
| -rw-r--r-- | docs/ref/models/querysets.txt | 26 |
5 files changed, 0 insertions, 62 deletions
diff --git a/docs/ref/models/database-functions.txt b/docs/ref/models/database-functions.txt index 494c175843..d39ed5001b 100644 --- a/docs/ref/models/database-functions.txt +++ b/docs/ref/models/database-functions.txt @@ -178,10 +178,6 @@ Django usually uses the databases' extract function, so you may use any ``lookup_name`` that your database supports. A ``tzinfo`` subclass, usually provided by ``pytz``, can be passed to extract a value in a specific timezone. -.. versionchanged:: 2.0 - - Support for ``DurationField`` was added. - Given the datetime ``2015-06-15 23:30:01.000321+00:00``, the built-in ``lookup_name``\s return: @@ -274,8 +270,6 @@ Usage example:: .. class:: ExtractQuarter(expression, tzinfo=None, **extra) - .. versionadded:: 2.0 - .. attribute:: lookup_name = 'quarter' These are logically equivalent to ``Extract('date_field', lookup_name)``. Each @@ -517,8 +511,6 @@ Usage example:: .. class:: TruncQuarter(expression, output_field=None, tzinfo=None, **extra) - .. versionadded:: 2.0 - .. attribute:: kind = 'quarter' These are logically equivalent to ``Trunc('date_field', kind)``. They truncate @@ -938,8 +930,6 @@ spaces. .. class:: StrIndex(string, substring, **extra) -.. versionadded:: 2.0 - Returns a positive integer corresponding to the 1-indexed position of the first occurrence of ``substring`` inside ``string``, or 0 if ``substring`` is not found. @@ -1028,8 +1018,6 @@ Usage example:: Window functions ================ -.. versionadded:: 2.0 - There are a number of functions to use in a :class:`~django.db.models.expressions.Window` expression for computing the rank of elements or the :class:`Ntile` of some rows. diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt index a929e8a98f..fe4dc2c525 100644 --- a/docs/ref/models/expressions.txt +++ b/docs/ref/models/expressions.txt @@ -388,8 +388,6 @@ The ``Aggregate`` API is as follows: .. attribute:: window_compatible - .. versionadded:: 2.0 - Defaults to ``True`` since most aggregate functions can be used as the source expression in :class:`~django.db.models.expressions.Window`. @@ -417,10 +415,6 @@ and :ref:`filtering-on-annotations` for example usage. The ``**extra`` kwargs are ``key=value`` pairs that can be interpolated into the ``template`` attribute. -.. versionchanged:: 2.0 - - The ``filter`` argument was added. - Creating your own Aggregate Functions ------------------------------------- @@ -694,8 +688,6 @@ should avoid them if possible. Window functions ---------------- -.. versionadded:: 2.0 - Window functions provide a way to apply functions on partitions. Unlike a normal aggregation function which computes a final result for each set defined by the group by, window functions operate on :ref:`frames <window-frames>` and @@ -902,8 +894,6 @@ calling the appropriate methods on the wrapped expression. .. attribute:: contains_over_clause - .. versionadded:: 2.0 - Tells Django that this expression contains a :class:`~django.db.models.expressions.Window` expression. It's used, for example, to disallow window function expressions in queries that @@ -911,15 +901,11 @@ calling the appropriate methods on the wrapped expression. .. attribute:: filterable - .. versionadded:: 2.0 - Tells Django that this expression can be referenced in :meth:`.QuerySet.filter`. Defaults to ``True``. .. attribute:: window_compatible - .. versionadded:: 2.0 - Tells Django that this expression can be used as the source expression in :class:`~django.db.models.expressions.Window`. Defaults to ``False``. diff --git a/docs/ref/models/indexes.txt b/docs/ref/models/indexes.txt index 5cb4f4ea2f..a78423bd36 100644 --- a/docs/ref/models/indexes.txt +++ b/docs/ref/models/indexes.txt @@ -58,8 +58,6 @@ than 30 characters and shouldn't start with a number (0-9) or underscore (_). .. attribute:: Index.db_tablespace -.. versionadded:: 2.0 - The name of the :doc:`database tablespace </topics/db/tablespaces>` to use for this index. For single field indexes, if ``db_tablespace`` isn't provided, the index is created in the ``db_tablespace`` of the field. diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index 51a87fc632..cea73eb67f 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -147,10 +147,6 @@ Django quotes column and table names behind the scenes. See the :meth:`~django.db.models.query.QuerySet.latest` docs for more. - .. versionchanged:: 2.0 - - Support for a list of fields was added. - ``managed`` ----------- @@ -291,10 +287,6 @@ Django quotes column and table names behind the scenes. Default ordering also affects :ref:`aggregation queries <aggregation-ordering-interaction>`. - .. versionchanged:: 2.0 - - Support for query expressions was added. - .. warning:: Ordering is not a free operation. Each field you add to the ordering diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index b2f430d7bc..06f153fb8e 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -712,10 +712,6 @@ not having any author:: >>> Entry.objects.values_list('authors') <QuerySet [('Noam Chomsky',), ('George Orwell',), (None,)]> -.. versionchanged:: 2.0 - - The ``named`` parameter was added. - ``dates()`` ~~~~~~~~~~~ @@ -1737,10 +1733,6 @@ raised if ``select_for_update()`` is used in autocommit mode. PostgreSQL doesn't support ``select_for_update()`` with :class:`~django.db.models.expressions.Window` expressions. -.. versionchanged:: 2.0 - - The ``of`` argument was added. - ``raw()`` ~~~~~~~~~ @@ -2099,10 +2091,6 @@ Example:: If you pass ``in_bulk()`` an empty list, you'll get an empty dictionary. -.. versionchanged:: 2.0 - - The ``field_name`` parameter was added. - ``iterator()`` ~~~~~~~~~~~~~~ @@ -2167,10 +2155,6 @@ psycopg mailing list <https://www.postgresql.org/message-id/4D2F2C71.8080805%40d between the number of rows transferred and the data discarded if the loop is exited early. -.. versionchanged:: 2.0 - - The ``chunk_size`` parameter was added. - ``latest()`` ~~~~~~~~~~~~ @@ -2205,10 +2189,6 @@ given parameters. Note that ``earliest()`` and ``latest()`` exist purely for convenience and readability. -.. versionchanged:: 2.0 - - Support for several arguments was added. - .. admonition:: ``earliest()`` and ``latest()`` may return instances with null dates. Since ordering is delegated to the database, results on fields that allow @@ -2988,8 +2968,6 @@ in the database <database-time-zone-definitions>`. ``quarter`` ~~~~~~~~~~~ -.. versionadded:: 2.0 - For date and datetime fields, a 'quarter of the year' match. Allows chaining additional field lookups. Takes an integer value between 1 and 4 representing the quarter of the year. @@ -3216,8 +3194,6 @@ of the return value ``filter`` ~~~~~~~~~~ -.. versionadded:: 2.0 - An optional :class:`Q object <django.db.models.Q>` that's used to filter the rows that are aggregated. @@ -3428,8 +3404,6 @@ lookups or :class:`Prefetch` objects you want to prefetch for. For example:: ``FilteredRelation()`` objects ------------------------------ -.. versionadded:: 2.0 - .. class:: FilteredRelation(relation_name, *, condition=Q()) .. attribute:: FilteredRelation.relation_name |
