#15130: Model.validate_unique method doesn't take in account multi-db
--------------------------------------+-------------------------------------
Reporter: t2y | Owner:
Status: closed | Milestone: 1.3
Component: ORM aggregation | Version: 1.2
Resolution: worksforme | Keywords: multi-db
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by ramiro):
* status: new => closed
* resolution: => worksforme
* summary: Model.validate_unique method is not considered with multi-db
=> Model.validate_unique method doesn't take in
account multi-db
Comment:
I've added tests (against trunk) that exercise the `unique` and
`unique_for_(date,month,year)` field options plus the
`Meta.unique_together` option by saving identical model instances to
different databases. Saving is successful so I can't reproduce this at the
ORM level.
I'm going to close this ticket as ''works for me''. If you can describe
better your use case (bonus points if they are a modification to the
attached tests) your scenario, please reopen. I suspect this might be a
problem in another part of the stack (admin app?) instead, or maybe I
forgot to test some condition?.
--
Ticket URL: <http://code.djangoproject.com/ticket/15130#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
