#31277: System check fields.E340 should be relaxed when DATABASE_ROUTERS is
present
-------------------------------------+-------------------------------------
Reporter: Xavier | Owner: nobody
Francisco |
Type: Bug | Status: new
Component: Core | Version: 3.0
(System checks) | Keywords: database-router,
Severity: Normal | manytomany
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hey.
On PR https://github.com/django/django/pull/11630, changes were made to
change to allow for multiple models with the same `db_name`. Instead of an
`Error` (`models.E028`), a `Warning` was created to be used in lieu of it,
when `DATABASE_ROUTERS` is present.
The same issue arises, with a different check, when using
`ManyToManyField`, with clashing `db_name`s. The system check in question
is `fields.E340`.
My suggestion would be to do apply the same change for this check, and
raise a `Warning` instead, whenever `DATABASE_ROUTERS` exists.
At this point, the only workaround is silencing the error system check.
--
Ticket URL: <https://code.djangoproject.com/ticket/31277>
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/049.1b9f934dec456ef2c5f12913dc139a59%40djangoproject.com.
