Browse files

[1.6.x] Documentation - Noted that OneToOneField doesn't respect unique.

Added OneToOneField to the list of model fields for which the unique
argument isn't valid. (OneToOneFields are inherently unique, and if
the user supplies a value for unique it is ignored / overwritten.)
  • Loading branch information...
1 parent 12d364a commit e7d4d41a30b4cf60690fe55e47b4e10403fc8b46 @marfire marfire committed with ptone Aug 20, 2013
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/ref/models/fields.txt
4 docs/ref/models/fields.txt
@@ -272,8 +272,8 @@ you try to save a model with a duplicate value in a :attr:`~Field.unique`
field, a :exc:`django.db.IntegrityError` will be raised by the model's
:meth:`` method.
-This option is valid on all field types except :class:`ManyToManyField` and
+This option is valid on all field types except :class:`ManyToManyField`,
+:class:`OneToOneField`, and :class:`FileField`.
Note that when ``unique`` is ``True``, you don't need to specify
:attr:`~Field.db_index`, because ``unique`` implies the creation of an index.

0 comments on commit e7d4d41

Please sign in to comment.