#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: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: needsinfo
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):
That sounds good to me. I'm sure that's going to be helpful for those
encountering the same situation.
I used the following sql to find out the columns and table names that are
potential at risk for this issue.
{{{
select table_name,
LENGTH(table_name) as l
from USER_TABLES
where LENGTH(table_name) = 30
and table_name not like 'DM$%'
/
select TABLE_NAME,
COLUMN_NAME,
LENGTH(COLUMN_NAME) as l
from USER_TAB_COLUMNS
where LENGTH(COLUMN_NAME) = 30
and table_name not like 'DM$%'
/
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33789#comment:8>
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/010701818054b390-b03f0e99-5760-4d12-a51c-be472b9a83ea-000000%40eu-central-1.amazonses.com.
