| commit | 2590c69d965a85fd3a2944bcdf0e07e146eae661 | |
| author | mtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37> | |
| Sat, 23 Aug 2008 16:56:41 +0000 (23 16:56 +0000) | ||
| committer | mtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37> | |
| Sat, 23 Aug 2008 16:56:41 +0000 (23 16:56 +0000) | ||
| tree | 882a8fa1f90b89792f6cc520b8930dea1ec512a9 | treesnapshot (tar.gz zip) |
| parent | 85182fd60e4931f0113c6401cc006c58e2a7f3a2 | commitdiff |
Fixed #7042 -- The management validation command nows alerts users to 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
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
| django/core/management/validation.py | diffblobblamehistory | |
| tests/modeltests/invalid_models/models.py | diffblobblamehistory |