Skip to content
Browse files

Merge pull request #1039 from cannona/master

Clarified what unique_for_date considers
  • Loading branch information...
2 parents 9db4c2c + 291250f commit 8035533557aad2cac54e92bd851f2a5d792150fa @timgraham timgraham committed
Showing with 4 additions and 0 deletions.
  1. +1 −0 AUTHORS
  2. +3 −0 docs/ref/models/fields.txt
@@ -121,6 +121,7 @@ answer newbie questions, and generally made Django that much better:
Chris Cahoon <>
Juan Manuel Caicedo <>
Trevor Caira <>
+ Aaron Cannon <>
Brett Cannon <>
Ricardo Javier Cárdenes Medina <>
Jeremy Carbaugh <>
3 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.

0 comments on commit 8035533

Please sign in to comment.
Something went wrong with that request. Please try again.