Commit Graph

8 Commits

Author SHA1 Message Date
Jan Provaznik 0fc9f9d3e7 Add version 4.2 to all existing migrations
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
2018-11-22 13:18:28 +01:00
Gabriel Mazetto f21e655b61 disable_statement_timeout doesn't require any argument anymore
it will decide the method for disable statement_timeout upon
per transaction or per session, based on how it's called.

When calling with a block, block will be executed and it will use
session based statement_timeout, otherwise will default to existing
behavior.
2018-08-11 04:15:59 +02:00
Gabriel Mazetto 119c49172f Fix specs to use `disable_statement_timeout` correctly 2018-08-10 20:40:00 +02:00
Sean McGivern d8be981466 Prevent update_column_in_batches on large tables
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.
2017-11-17 16:56:50 +00:00
Grzegorz Bizon 3ad076b7e9 Disable statement timeout in CI pipelines migration 2017-06-19 14:45:50 +02:00
Rémy Coutable b8b9ed55df Disable Migration/UpdateColumnInBatches for old migrations
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-05-29 11:28:23 +02:00
Lin Jen-Shin 20ece0aac3 Disable transaction for updating the table 2017-05-15 16:22:29 +08:00
Lin Jen-Shin b5bffbd4ad Move to post_migrate and use update_column_in_batches 2017-05-15 14:48:24 +08:00