Is it possible to upgrade from migrate 2.2.0 to 2.27.0 without nuking the whole DB?
j
janpio
07/16/2021, 3:09 PM
Of course, all migrations can be edited in all cases anyway.
But the details depend totally on your specific case and how you created your database in the first place.
j
Jon Deibel
07/16/2021, 3:40 PM
I mean I have an existing migration setup at 2.2.0 and when I try to upgrade to 2.27 and re-setup the migration folder or re-init it, it wants to nuke all the data in my database
Jon Deibel
07/16/2021, 3:40 PM
Perhaps I am using the wrong commands to re-setup the migration process
j
janpio
07/16/2021, 3:41 PM
If you are fine with loosing your old files, "baselining" is the right thing to search for I think.
janpio
07/16/2021, 3:42 PM
If you have an existing database schema you are happy with, maybe also remove your current schema file and recreate it with Introspection to get rid of any old inconsistencies that might be in there.
janpio
07/16/2021, 3:42 PM
(Make sure to have Git or backups before you do any of that of course)