#27843: M2M db table names with explicit `username`
-------------------------------------+-------------------------------------
Reporter: felixxm | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 1.11
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
`db.models.fields.related._get_m2m_db_table` doesn't work properly if we
use `db_table` with explicit `username` of a length between 24-30 chars
e.g.
{{{
db_table = "d4_pullrequestsoracle_35"."DJANGO_DOCUMENT_TABLE"
name = 'students'
}}}
then `_get_m2m_db_table` returns `"D4_PULLREQUESTSORACLE_35".56C8"`
instead of `"D4_PULLREQUESTSORACLE_35"."DJANGO_DOCUMENT_TABLE_STUDENTS"`.
--
Ticket URL: <https://code.djangoproject.com/ticket/27843>
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.3ceff1e617b0d75cb7e8c61f9c56e1cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
