Migrating Applications
Posted: Wed Feb 19, 2025 7:41 pm
Hello, as an old timer of application development, I am used to a develop, test and production environment.
With the provided Backup function it is easy to clone a develop database from a production database. As is a test database.
What I currently have to do manually is to delete all tables in the develop database but the zzzz tables, backup these and delete manually all zzzzz tables from the test database in order to import the backup containing the zzzzz tables only. And by doing this copy the develoment version of the application into the test environment for acceptance testing. In a similar action I can go back to a prvious application version.
My question: Wouldn't it be a good idea to add two functions: One to backup the application data (zzzz tables) and one to wipe the current application data and load a different appliction set/version? It would also allow during development to save a "checkpoint" while making changes.
Or is there a (good) reason, I do not see, for NOT executing the steps as I do
With the provided Backup function it is easy to clone a develop database from a production database. As is a test database.
What I currently have to do manually is to delete all tables in the develop database but the zzzz tables, backup these and delete manually all zzzzz tables from the test database in order to import the backup containing the zzzzz tables only. And by doing this copy the develoment version of the application into the test environment for acceptance testing. In a similar action I can go back to a prvious application version.
My question: Wouldn't it be a good idea to add two functions: One to backup the application data (zzzz tables) and one to wipe the current application data and load a different appliction set/version? It would also allow during development to save a "checkpoint" while making changes.
Or is there a (good) reason, I do not see, for NOT executing the steps as I do