#24407: Initial migration fails if app name has upper-case letters on Oracle
----------------------------+------------------------------------
Reporter: CarstenF | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
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
----------------------------+------------------------------------
Changes (by shaib):
* keywords: => oracle
Comment:
While it is different in symptoms and code-paths, this is essentially the
same issue as #20487: The Oracle backend (not Oracle itself) converts
names to uppercase on the way into the db, and so it must convert them
back to lowercase on the way out -- which, in some cases, is not the
correct transformation.
The right workaround for you is, of course, to fake the initial migration.
I'm not closing this as a dupe (yet), because the migrations behavior
deserves more careful study.
--
Ticket URL: <https://code.djangoproject.com/ticket/24407#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.8a869c4314e353e863aaad844610b98f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
