From 43a4835edf32c57eb74c0eb207c276734a34abcf Mon Sep 17 00:00:00 2001 From: Daniel Hahler Date: Wed, 23 Nov 2016 16:36:11 +0100 Subject: Fixed #27473 -- Added DurationField support to Extract. --- docs/ref/models/database-functions.txt | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/models/database-functions.txt b/docs/ref/models/database-functions.txt index 9bb36ccafd..acddc7cbe4 100644 --- a/docs/ref/models/database-functions.txt +++ b/docs/ref/models/database-functions.txt @@ -331,12 +331,16 @@ We'll be using the following model in examples of each function:: Extracts a component of a date as a number. -Takes an ``expression`` representing a ``DateField`` or ``DateTimeField`` and a -``lookup_name``, and returns the part of the date referenced by ``lookup_name`` -as an ``IntegerField``. 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. +Takes an ``expression`` representing a ``DateField``, ``DateTimeField``, +``TimeField``, or ``DurationField`` and a ``lookup_name``, and returns the part +of the date referenced by ``lookup_name`` as an ``IntegerField``. +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: -- cgit v1.3