Commit 291250f7 authored by Aaron Cannon's avatar Aaron Cannon
Browse files

Added clarification to the docs, pointing out that unique_for_date only... 

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

AUTHORS

+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>

docs/ref/models/fields.txt

+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``