mirror of https://github.com/django/django.git
Fixed #20409 -- Clarified how unique_for_date works when USE_TZ is set.
This commit is contained in:
parent
be9930d7be
commit
01edcf70f2
|
@ -291,7 +291,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
|
||||
<default-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
|
||||
|
|
Loading…
Reference in New Issue