#15130: Model.validate_unique method doesn't take in account multi-db
-------------------------------------+-------------------------------------
Reporter: Tetsuya Morimoto | Owner: (none)
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 François Granade):
I got badly bitten by this bug in #33912, and I think that there are two
issues, related but not the same, here -
1) the current behavior (validating against the default database for
object that live in another database) does not make sense
2) it should be be possible to define against what DB the validation
happens.
To me, the first issue is a very serious bug, and the second a useful
feature.
What about fixing the first one first ? For that, the patch 15130.2.diff
above would work.
What would be needed for this patch to be accepted ? I can clean it up
--
Ticket URL: <https://code.djangoproject.com/ticket/15130#comment:23>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018287cd4273-2dc0e85b-5e36-4928-b091-02743ebc3899-000000%40eu-central-1.amazonses.com.
