Added clarification to the docs, pointing out that unique_for_date only considers the date portion of DateTime fields.

This commit is contained in:
Aaron Cannon 2013-05-03 08:46:53 -05:00
parent d48b7230a8
commit 291250f7b6
2 changed files with 4 additions and 0 deletions

View file

@ -287,6 +287,9 @@ For example, if you have a field ``title`` that has
``unique_for_date="pub_date"``, then Django wouldn't allow the entry of two
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.
This is enforced by model validation but not at the database level.
``unique_for_month``