what do you mean by "using deprecated code"?
I mean migration files which has deprecated code or something that is removed on new version
Ohh not realy, you can squash old migrations instead
I see, that should be what I should do instead of manually updating migration files that are auto generated right ??
i think is easier to mantain
should I squash all migrations to one
yes, unless you know some of them have not been applied on production (or any environment other than your local)
I think I should go yo old version, squash migrations and come to new versions as its throwing error as some codes in migrations doesnt exist on django 5
but you just need to update one migration file
in this case yes, I was saying that in general case where we need to change multiple files
Обсуждают сегодня