#30673: Django throws error when different apps with different models have the
same
name table name.
-------------------------------------+-------------------------------------
Reporter: Cubed | Owner: Adnan
| Umer
Type: Bug | Status: assigned
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adnan Umer):
* owner: nobody => Adnan Umer
* status: new => assigned
Comment:
I agree with your opinion. Assigning to myself, patch on its way
Replying to [comment:1 Claude Paroz]:
> Regression in [5d25804eaf81795c7d457e5a2a9f0b9b0989136c], ticket #20098.
> My opinion is that as soon as the project has a non-empty
`DATABASE_ROUTERS` setting, the error should be turned into a warning, as
it becomes difficult to say for sure that it's an error. And then the
project can add the warning in `SILENCED_SYSTEM_CHECKS`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30673#comment:2>
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/067.9e7ed9e30f90f9f33791ee9635c1cd36%40djangoproject.com.
