Re: [Django] #27417: Change case on field causes invalid rename on Oracle backend migration

[Django]

#27417: Change case on field causes invalid rename on Oracle backend migration
-+-
 Reporter:  Vackar Afzal |Owner:  Zach
 |  Zundel
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:  Migrations, Oracle,  | Triage Stage:
  DB, Rename |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zach Zundel):

 * owner:  nobody => Zach Zundel
 * status:  new => assigned


--
Ticket URL: 
Django 
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/069.04195659176e81b120d7773c73fbfc24%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27417: Change case on field causes invalid rename on Oracle backend migration

[Django]

#27417: Change case on field causes invalid rename on Oracle backend migration
-+-
 Reporter:  Vackar Afzal |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:  Migrations, Oracle,  | Triage Stage:
  DB, Rename |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vackar Afzal):

 * type:  Uncategorized => Bug


--
Ticket URL: 
Django 
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/069.f0862ab19c4e959aa1195bd772f0130e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27417: Change case on field causes invalid rename on Oracle backend migration

[Django]

#27417: Change case on field causes invalid rename on Oracle backend migration
-+-
   Reporter:  Vackar |  Owner:  nobody
  Afzal  |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  1.9
  Migrations |
   Severity:  Release|   Keywords:  Migrations, Oracle,
  blocker|  DB, Rename
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 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.

--
Ticket URL: 
Django 
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/054.a16012967b820667b7857d743930f137%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.