An error occurred fetching the project authors.
- 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
-
- 11 Dec, 2017 1 commit
-
-
Sean McGivern authored
remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration.
-
- 17 Nov, 2017 1 commit
-
-
Sean McGivern authored
add_column_with_default is implemented in terms of update_column_in_batches, but update_column_in_batches can be used independently. Neither of these should be used on the specified large tables, because they will cause issues on large instances like GitLab.com. This also ignores the cop for all existing migrations, renaming AddColumnWithDefaultToLargeTable where appropriate.
-
- 28 Apr, 2017 1 commit
-
-
Robert Speicher authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 01 Sep, 2016 1 commit
-
-
Felipe Artur authored
-