- 22 Nov, 2018 1 commit
-
-
Jan Provaznik authored
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
-
- 25 Jul, 2018 1 commit
-
-
Lin Jen-Shin authored
-
- 09 Jun, 2016 1 commit
-
-
Sean McGivern authored
Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file.
-
- 08 Jun, 2016 1 commit
-
-
Yorick Peterse authored
This improves performance of the duplicate notification settings migration by removing duplicates in batches instead of using one big "DELETE FROM" query. The previous query would locally run over 45 minutes without even finishing. This new setup finished in a matter of seconds. Fixes #18289
-
- 03 Jun, 2016 1 commit
-
-
Felipe Artur authored
-