#30673: Django throws error when different apps with different models have the
same
name table name.
-------------------------------------+-------------------------------------
Reporter: Cubed | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 2.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Error message:
table_name: (models.E028) db_table 'table_name' is used by multiple
models: base.ModelName, app2.ModelName.
We have a Base app that points to a central database and that has its own
tables. We then have multiple Apps that talk to their own databases. Some
share the same table names.
We have used this setup for a while, but after upgrading to Django 2.2
we're getting an error saying we're not allowed 2 apps, with 2 different
models to have the same table names.
Is this correct behavior? We've had to roll back to Django 2.0 for now.
--
Ticket URL: <https://code.djangoproject.com/ticket/30673>
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/052.34733b65b9f3a928f107113021d4ad58%40djangoproject.com.
