#15130: Model.validate_unique method doesn't take in account multi-db
-------------------------------------+-------------------------------------
Reporter: t2y | Owner:
Type: Bug | Status: new
Component: Database layer | Version: 1.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: multi-db | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
Did you see the solution proposed in attachment:15130.2.diff? That seems
on the right track to me. I don't see why the programmer should have to
specify the database when we already have database routers to figure out
where the model will be saved?
--
Ticket URL: <https://code.djangoproject.com/ticket/15130#comment:16>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.365a730321c4969ff75c25f558da1965%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
