#29092: Clashing table name checks don't account for database routers
-------------------------------------+-------------------------------------
Reporter: Elizaveta | Owner: nobody
Kishchukova |
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
* type: Uncategorized => Bug
Comment:
Feel free to reopen and offer a patch for evaluation if you think the
implementation is straightforward. I guess any solution can't be perfect
since we won't have access to the `instance` hint at check time.
--
Ticket URL: <https://code.djangoproject.com/ticket/29092#comment:3>
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/064.6f923058a9ffa55dfa184bd72f940c93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.