summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Cannon <cannona@fireantproductions.com>2013-05-03 08:46:53 -0500
committerAaron Cannon <cannona@fireantproductions.com>2013-05-03 08:46:53 -0500
commit291250f7b66a6b81d2fc64eecc82cb2b4bd6c090 (patch)
tree293d9e6eb0420b28c91173ec44959fe59bd8f1d0
parentd48b7230a8b8d44607b19749fb4a0a8a25d50cf1 (diff)
Added clarification to the docs, pointing out that unique_for_date only considers the date portion of DateTime fields.
-rw-r--r--AUTHORS1
-rw-r--r--docs/ref/models/fields.txt3
2 files changed, 4 insertions, 0 deletions
diff --git a/AUTHORS b/AUTHORS
index 8cd86d38dc..fb084f26cb 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -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>
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index d322904ec9..99ba78cb09 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -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``