Re: [Django] #35176: Renaming a field and its verbose name results in deleting and recreating a new column in django 4.2

[Django]

#35176: Renaming a field and its verbose name results in deleting and 
recreating a
new column in django 4.2
--+--
 Reporter:  Corentin Bettiol  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  4.2
 Severity:  Normal|   Resolution:
 Keywords:  rename, renaming  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Corentin Bettiol):

 * Attachment "0003_remove_mymodel_another_field_and_more.py" added.

 Nonworking migration: the field "another_field" was deleted, and a new
 field named "another_field_renamed" was created. Only difference with the
 previous migration is that the verbose_name of the field also changed.
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d885897ba-0b8f850b-a1be-44eb-a6c3-2c9596bb8d99-00%40eu-central-1.amazonses.com.

Re: [Django] #35176: Renaming a field and its verbose name results in deleting and recreating a new column in django 4.2

[Django]

#35176: Renaming a field and its verbose name results in deleting and 
recreating a
new column in django 4.2
--+--
 Reporter:  Corentin Bettiol  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  4.2
 Severity:  Normal|   Resolution:
 Keywords:  rename, renaming  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Corentin Bettiol):

 * Attachment "0002_rename_a_field_mymodel_a_field_renamed.py" added.

 Working rename of a field: field "a_field" was renamed "a_field_renamed",
 using migrations.RenameField.
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d8857e18a-c5c57cb5-eca1-46f9-93a2-2efc4d7a1816-00%40eu-central-1.amazonses.com.

Re: [Django] #35176: Renaming a field and its verbose name results in deleting and recreating a new column in django 4.2

[Django]

#35176: Renaming a field and its verbose name results in deleting and 
recreating a
new column in django 4.2
--+--
 Reporter:  Corentin Bettiol  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  4.2
 Severity:  Normal|   Resolution:
 Keywords:  rename, renaming  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Corentin Bettiol):

 * Attachment "0001_initial.py" added.

 First migration: create the model in db, with 2 fields.
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d8857067b-3d70e4c8-ad5e-456b-9a93-b7fda0459a82-00%40eu-central-1.amazonses.com.