Re: [Django] #33789: Table and colums with more then 30 chars can no longer be found on Oracle. (was: Table and colums with more then 30 chars can no longer be found / queried after migrating from django 3.2 to 4.0 using an Oracle backend)

[Django]

#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 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?

--
Ticket URL: <https://code.djangoproject.com/ticket/33789#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.