Commit 80355335 authored by Tim Graham's avatar Tim Graham
Browse files

Merge pull request #1039 from cannona/master

Clarified what unique_for_date considers
parents 9db4c2c1 291250f7
Loading
Loading
Loading
Loading
+1 −0
Original line number Diff line number Diff line
@@ -121,6 +121,7 @@ answer newbie questions, and generally made Django that much better:
    Chris Cahoon <chris.cahoon@gmail.com>
    Juan Manuel Caicedo <juan.manuel.caicedo@gmail.com>
    Trevor Caira <trevor@caira.com>
    Aaron Cannon <cannona@fireantproductions.com>
    Brett Cannon <brett@python.org>
    Ricardo Javier Cárdenes Medina <ricardo.cardenes@gmail.com>
    Jeremy Carbaugh <jcarbaugh@gmail.com>
+3 −0
Original line number Diff line number Diff line
@@ -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``