OK, I just uploaded a patch against trunk that should be consistent with this discussion. As I note in the ticket, I kept the tests from the prior patch, which tests were specifically relevant to the admin as reported by the original ticket, but I also added additional, more focused tests. I also had to modify one of the model_formsets tests, as it was assuming the old behavior.
I ran my changes against the whole of the Django test suite, and no relevant errors seem to have been generated. I hope this is OK to check in :) Regards, Eduardo On Apr 27, 3:13 pm, Carl Meyer <c...@oddbird.net> wrote: > On 04/27/2011 02:02 PM, legutierr wrote: > > > Ok, I'll create a patch soon (with tests + documentation) that > > hopefully works for you. I don't think it will be very complicated > > implementation-wise, just a few additional lines, I think. With > > regards to the documentation, I'll add a note here: > > >http://docs.djangoproject.com/en/1.3/ref/models/options/#unique-together > > > and here: > > >http://docs.djangoproject.com/en/1.3/ref/models/instances/#django.db.... > > > Including a note saying that the behavior has changed > > Great, thanks. I think this behavior change only needs to be described > in one place (the validate_unique docs), but the text at the former link > is actually inaccurate ever since model validation - it should be > updated to mention that unique_together is also checked by model > validation, with a link to the validate_unique docs. > > Carl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
