diff options
| author | Tim Graham <timograham@gmail.com> | 2013-05-14 16:01:24 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-05-14 16:01:24 -0700 |
| commit | 8035533557aad2cac54e92bd851f2a5d792150fa (patch) | |
| tree | bffe21a8281d05c55b6b80c39de16bbdd55bd569 /docs/ref | |
| parent | 9db4c2c1337aa3c000abaeb0d8024351dbc643d7 (diff) | |
| parent | 291250f7b66a6b81d2fc64eecc82cb2b4bd6c090 (diff) | |
Merge pull request #1039 from cannona/master
Clarified what unique_for_date considers
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/fields.txt | 3 |
1 files changed, 3 insertions, 0 deletions
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`` |