#32653: Quoting names in the Oracle backend is not consistent with the db_table
generation.
-------------------------------------+-------------------------------------
Reporter: Javier Buzzi | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Javier Buzzi):
@Mariusz the issue is see with your solution is that it will work from my
current case Postgres as `default`, Oracle as `old`. Where Postgres wont
change the db_table as long as its under 63 chars??? But if we have the
inverse, Oracle as `default` and Postgres as `new`; it will break Postgres
since the `db_table` would be something like
`backends_verylongmodelnamezzz1234` and Postgres would want the whole
string
`backends_verylongmodelnamezzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz`.
The solution @Simon suggested would work on both cases.
--
Ticket URL: <https://code.djangoproject.com/ticket/32653#comment:5>
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/069.1e50c5595056e5a0a3c63bbb7adde2e2%40djangoproject.com.
