#25902: Add system check for project-wide database table name conflicts
--------------------------------------+------------------------------------
Reporter: amosonn | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
I think the argument for having this check outside of the migrations
framework is that if you are combining existing third-party apps, you
won't necessarily be generating migrations for them. The check might go in
`django/django/db/models/base.py` (see the `check()` method). There would
need to be a global registry of tables names.
We likely can't change the default table names that Django generates for
backwards compatibility reasons.
--
Ticket URL: <https://code.djangoproject.com/ticket/25902#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 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/065.9cd7d1fce3f534b47ce7bfb45d047ec0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
