#27417: Migration to change model field case crashes on Oracle
-------------------------------------+-------------------------------------
Reporter: Vackar Afzal | Owner: Zach
| Zundel
Type: Bug | Status: assigned
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: Migrations, Oracle, | Triage Stage: Accepted
DB, Rename |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Shai Berger):
I'd consider marking this a duplicate, just one more manifestation of the
case issues (e.g. #20487, #20226).
There's a fine point here: The case insensitivity is actually not a
feature of the Oracle database engine, but rather of the Django Oracle
backend. The intention was good -- when you write object (table, column,
even user) names without quotes, Oracle understands them as upper case,
and so Oracle DBAs have grown used to seeing all these names uppercased;
the Django backend developers, I assume, wanted to be friendly to them.
The result, however, is problematic (I have referred to it in the past as
"case insanity"), and although I tried, I see no way to fix it in a
reasonably backwards-compatible way.
It may be possible and may be helpful to solve this specific instance of
the problem without solving the more general issue, so maybe we should
leave it be. However, I would vote against adding case-sensitivity
feature-flags are any such device to the generic database backends. As far
as I know, none of the database products Django support (in core or
through 3rd party modules) is actually case-insensitive.
--
Ticket URL: <https://code.djangoproject.com/ticket/27417#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.ac8d4d15fb218fcc65f850b6a7250c00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
