David Taylor e76c583b91 DEV: Promote old post-deploy migrations to pre-deploy migrations (#13477) ... Having a large number of post-deploy migrations running out-of-numerical-sequence with pre-deploy migrations can be problematic. For example, if we have the sequence - db/migrate/2017... - add column - db/post_migrate/2018... - drop the column - db/migrate/2021... - add the same column again It will work fine in numerical order. But if you run the pre-deploy migrations **followed by** the post-deploy migrations, you will not get the same result. Our post-deploy system is designed to allow for seamless upgrades of Discourse. However, it is reasonable for us to only support this totally seamless experience for a limited period of time. This commit moves all post_deploy migrations which are more than 1 year old (i.e. more than 2 major Discourse versions ago) into the regular pre-deploy migrations directory. This limits the impact of any edge cases caused by out-of-numerical-sequence migrations.		2021-06-22 16:02:24 +01:00
..
base_dropper.rb	DEV: Upgrade Rails to 6.1.3.1 (#12688)	2021-04-21 12:36:32 +03:00
column_dropper.rb	FIX: Create readonly functions during backup	2019-08-09 11:39:46 +02:00
safe_migrate.rb	DEV: Promote old post-deploy migrations to pre-deploy migrations (#13477)	2021-06-22 16:02:24 +01:00
table_dropper.rb	FIX: Drop readonly function when dropping table	2019-08-09 11:39:46 +02:00