discourse/lib/migration
Sam Saffron e2284cf739
Revert "We have had errors reported due to migrations breaking and are reverting"
This reverts commit 8b46f14744.

It corrects the reason for the revert:

We rely on SafeMigrate existing cause we call it from migrations,
Zeitwerk will autoload it.

Instead of previous pattern we explicitly bypass all the hacks in
production mode.

We need to disable SafeMigrate cause it is not thread safe.

A thread safe implementation is possible but not worth the effort,
we catch the issues in dev and test.
2020-04-14 11:31:07 +10:00
..
base_dropper.rb FIX: Create readonly functions during backup 2019-08-09 11:39:46 +02:00
column_dropper.rb FIX: Create readonly functions during backup 2019-08-09 11:39:46 +02:00
safe_migrate.rb Revert "We have had errors reported due to migrations breaking and are reverting" 2020-04-14 11:31:07 +10:00
table_dropper.rb FIX: Drop readonly function when dropping table 2019-08-09 11:39:46 +02:00