From 83e434a2c2910d9e0540ea693d5f65e6550240c1 Mon Sep 17 00:00:00 2001 From: Kevin Christopher Henry Date: Tue, 20 Aug 2013 23:22:25 -0400 Subject: [PATCH] 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.) --- docs/ref/models/fields.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index a9673ce3d20..6ef487e90f1 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -281,8 +281,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:`~django.db.models.Model.save` method. -This option is valid on all field types except :class:`ManyToManyField` and -:class:`FileField`. +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.