#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
--------------------------------------+------------------------------------
Changes (by timgraham):
* type: Uncategorized => New feature
* component: Database layer (models, ORM) => Core (System checks)
* version: 1.9 => master
* stage: Unreviewed => Accepted
Comment:
I guess we might be able to add a system check for these sort of clashes,
but it might be a non-trivial amount of work for what I assume isn't a
very common case. Also, such validation would need to account for the
possibility that a user does want two models to use the same database
table. Probably `Meta.db_table` would be set by the user in such cases. Do
you have any other ideas? #12810 is another ticket about checks for
clashing many-to-many tables.
--
Ticket URL: <https://code.djangoproject.com/ticket/25902#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 [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.d86eef191830e7bdb75e65764f7c1dff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
