Whenever a new table, view, trigger, etc. is added, the SQL for this will need to be added both to the setup SQL script and to a migration SQL script, which seems silly.
Perhaps the setup script should be separated into stages, with the migration script running the setup script for the new stage before running its own SQL to fix anything amiss.
Whenever a new table, view, trigger, etc. is added, the SQL for this will need to be added both to the setup SQL script and to a migration SQL script, which seems silly.
Perhaps the setup script should be separated into stages, with the migration script running the setup script for the new stage before running its own SQL to fix anything amiss.