Changes between Version 1 and Version 2 of Ticket #24040
- Timestamp:
- Dec 22, 2014, 9:23:17 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24040
- Property Severity Release blocker → Normal
-
Ticket #24040 – Description
v1 v2 1 1 I cant imagine this is not a known issue, but I havent been able to find it. Please show me the duplicate if there is one. 2 3 EDIT: https://docs.djangoproject.com/en/dev/ref/databases/#naming-issues. 4 5 I still think is is unnecessarily confusing. The hash is created to comply with the oracle 32-char backend, but as wel all know that this hash has a 100% guarantee on failure, why not catch this error ini django instead of sending bad data over the line 6 2 7 3 8 If I create a model (django dev, oracle 11.2 backend), the sql statement is distorted if the db_table is over 31 characters. Almost like a buffer overflow: