#20098: Django validate command fails to detect that multiple models declare the
same db_table
-------------------------------------+-------------------------------------
Reporter: carsten.klein@… | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.5
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Keryn Knight <django@…>):
It is worth bearing in mind that there are valid use cases for
encountering duplicate table names, such as when using proxy models, or
unmanaged models. The provided patch doesn't seem to account for that, but
I'm not familiar enough with the surrounding code to know whether it is
already handled.
--
Ticket URL: <https://code.djangoproject.com/ticket/20098#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
