HTTPS clone URL

Subversion checkout URL

… the
presence (and incorrectness) of unique=True on ManyToManyFields. This has never
worked and generates invalid SQL. Now it's raised as an explicit error during
validation. Thanks to clamothe for the patch.
Still needs a docs change to make this clear, but that goes to the docs
refactor branch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8488 bcc190cf-cafb-0310-a4f2-bffc1f526a37

e.add(opts, "Reverse query name for field '%s' clashes with related field '%s.%s'. Add a related_name argument to the definition for '%s'."% (f.name, rel_opts.object_name, r.get_accessor_name(), f.name))

- seen_intermediary_signatures = []

+ seen_intermediary_signatures = []

for i, f inenumerate(opts.local_many_to_many):

# Check to see if the related m2m field will clash with any

# existing fields, m2m fields, m2m related objects or related

@@ -110,6 +110,11 @@ def get_validation_errors(outfile, app=None):

# so skip the next section

ifisinstance(f.rel.to, (str, unicode)):

continue

+

+ # Check that the field is not set to unique. ManyToManyFields do not support unique.