#30673: Django throws error when different apps with different models have the
same
name table name.
-------------------------------------+-------------------------------------
Reporter: Cubed | Owner: Adnan
| Umer
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"8d3519071ec001f763b70a3a1f98ae2e980bd552" 8d351907]:
{{{
#!CommitTicketReference repository=""
revision="8d3519071ec001f763b70a3a1f98ae2e980bd552"
Fixed #30673 -- Relaxed system check for db_table collision when database
routers are installed by turning the error into a warning.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30673#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.6b22cfd4fc9911b0da8580b6281f7f9b%40djangoproject.com.
