#33789: Table and colums with more then 30 chars can no longer be found on
Oracle.
-------------------------------------+-------------------------------------
Reporter: Paul in 't Hout | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Paul in 't Hout):
Replying to [comment:2 Mariusz Felisiak]:
> Yes, this behavior was intentionally changed in
1f643c28b5f2b039c47155692844dbae1cb091cd. Unfortunately, the previous
implementation of `quote_name()` on Oracle was also buggy and not
consistent with `db_table`. Do you have manually specified `db_table`
names? We can document this change in 4.0 release notes with the
recommendation to specify `db_table` in such cases. What do you think?
We do use db_table in Model.Meta. I can update those to use full UPPER
notation of the table_name, I suppose that should address the table name
truncation.
Is there a similar workaround that can be used for column names ?
--
Ticket URL: <https://code.djangoproject.com/ticket/33789#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701816ddf494d-7862720d-b956-43be-b4f2-9b5de4d97c7b-000000%40eu-central-1.amazonses.com.
