Django migrations.RenameField creating new field instead of renaming existing one

Question

I edited a fresh migration file to instead of adding a new field, just rename a field that already exists on the Django Model

This was the only change on this field

    migrations.RenameField(
        model_name='my_field',
        old_name='field_old_name',
        new_name='field_new_name',
    ),

But after running manage.py migrate, I notice that a new field was added (with a default field value) and the old one still there

And when running manage.py makemigrations again, it creates a migration to remove the old field

What I can't do, because I would lose the data

Steps:

new fields added to model (without removing old one to not break code)
manage.py makemigrations
code changed to use new field
migration file edited to use migrations.RenameField
manage.py migrate

Guilherme · Accepted Answer · 2022-06-01 15:47:35Z

1

Note: I decided to put this one here, because the problem wasn't that obvious

The issue was that I didn't have write permission on the migration file after generating it

So the editions I did, appeared on the VS Code, but weren't saved on the file So, the migrations applied when running manage.py migrate didn't had the RenameField command

Running sudo chmod -R 775 <project_folder> and sudo chown <user> -R <project_folder> solved

answered Jun 1, 2022 at 15:47

Guilherme

1,8851 gold badge27 silver badges47 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Django migrations.RenameField creating new field instead of renaming existing one

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related