From 38d6e1e2ada93e5d8c672ba18f1f8e3cd6c5ca76 Mon Sep 17 00:00:00 2001 From: Antoine Catton Date: Fri, 9 Oct 2015 10:55:19 -0600 Subject: [1.9.x] Fixed #25535 -- Made ForeignObject checks less strict. Check that the foreign object `from_fields` are a subset of any unique constraints on the foreign model. Backport of 80dac8c33e7f6f22577e4346f44e4c5ee89b648c and c7aff31397a7228f6ac2e33c10ebdf36c4b7a9b7 from master --- docs/ref/checks.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt index 208e3fb81f..3cd68a43c8 100644 --- a/docs/ref/checks.txt +++ b/docs/ref/checks.txt @@ -189,8 +189,9 @@ Related Fields for ````. * **fields.E306**: Related name must be a valid Python identifier or end with a ``'+'``. -* **fields.E310**: None of the fields ````, ````, ... on model - ```` have a ``unique=True`` constraint. +* **fields.E310**: No subset of the fields ````, ````, ... on + model ```` is unique. Add ``unique=True`` on any of those fields or + add at least a subset of them to a unique_together constraint. * **fields.E311**: ```` must set ``unique=True`` because it is referenced by a ``ForeignKey``. * **fields.E320**: Field specifies ``on_delete=SET_NULL``, but cannot be null. -- cgit v1.3