From e192739b3e3209a371a5d0f5f05fd083e88259f2 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Sat, 7 Sep 2013 14:08:54 -0500 Subject: [PATCH] Fixed #20409 -- Clarified how unique_for_date works when USE_TZ is set. --- docs/ref/models/fields.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index dd0d025ab2..1e3476166f 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -300,7 +300,9 @@ For example, if you have a field ``title`` that has records with the same ``title`` and ``pub_date``. Note that if you set this to point to a :class:`DateTimeField`, only the date -portion of the field will be considered. +portion of the field will be considered. Besides, when :setting:`USE_TZ` is +``True``, the check will be performed in the :ref:`current time zone +` at the time the object gets saved. This is enforced by :meth:`Model.validate_unique()` during model validation but not at the database level. If any :attr:`~Field.unique_for_date` constraint