#27417: Migration to change model field case crashes on Oracle
-------------------------------------+-------------------------------------
Reporter: Vackar Afzal | Owner: felixxm
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: Migrations, Oracle, | Triage Stage: Accepted
DB, Rename |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"e6b5108acc79dcff5bc90bc97500569c74a807bc" e6b5108]:
{{{
#!CommitTicketReference repository=""
revision="e6b5108acc79dcff5bc90bc97500569c74a807bc"
Fixed #27417 -- Made RenameField operation a noop for field name case
changes on Oracle.
Field names are always uppercased in the Oracle backend. Changing case
should be a noop to avoid database errors: "ORA-00957: duplicate column
name".
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27417#comment:7>
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.9bcb19ed1270d99879c6e2ab28be0cd3%40djangoproject.com.
