id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 27417,Migration to change model field case crashes on Oracle,Vackar Afzal,Mariusz Felisiak,"Given the following class {{{ class MyModel(models.Model): somefield = models.CharField(max_length=100) }}} if I rename 'somefield' to 'someField' and run make migrations, it will generate a migrations that will rename 'somefield' to 'someField' On case insensitive backends like oracle, this will result in the following invalid SQL being generated. {{{ alter table mymodel rename somefield to someField; }}} In cases like this, it should simply generate no SQL. The other option is when prompted for 'did you rename field x to y' , you can say no, which will result in a drop column followed by an add column, but this will result in **all of the existing data in the column being lost**, less than ideal.",Bug,closed,Migrations,1.9,Normal,fixed,"Migrations, Oracle, DB, Rename",,Accepted,1,0,0,0,0,0