#15130: Model.validate_unique method doesn't take in account multi-db
-------------------------------------------+--------------------------------
Reporter: t2y | Owner:
Status: reopened | Milestone: 1.3
Component: ORM aggregation | Version: 1.2
Resolution: | Keywords: multi-db
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
-------------------------------------------+--------------------------------
Comment (by ramiro):
`15130.3-tests.diff` contains new more granular tests (new model for
tests, separated the unique_for_{date,month,year} tests). It runs ten new
tests; five of them by saving first an instance to the 'default' database
and then trying to save an identical instance to the 'other' DB, and the
other five in the inverse order.
Theoretically all of them should fail before applying a fix for this
ticket, but only the five tests with the 'default', 'other' order do.
--
Ticket URL: <http://code.djangoproject.com/ticket/15130#comment:12>
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.
