p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #20409 -- Clarified how unique_for_date works when USE_TZ is set.

This commit is contained in:
Aymeric Augustin 2013-09-07 14:08:54 -05:00
parent 31e16c1343
commit e192739b3e
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ref/models/fields.txt
View File

@ -300,7 +300,9 @@ For example, if you have a field ``title`` that has
records with the same ``title`` and ``pub_date``. records with the same ``title`` and ``pub_date``.
Note that if you set this to point to a :class:`DateTimeField`, only the 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
<default-current-time-zone>` at the time the object gets saved.
This is enforced by :meth:`Model.validate_unique()` during model validation 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 but not at the database level. If any :attr:`~Field.unique_for_date` constraint