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
Lin Jen-Shin
b95da565cd
Enable rubocop for db/**/* and ee/db/**/*
2018-07-25 17:47:12 +08:00
Grzegorz Bizon
4737fc3bee
Decrease statuses batch size even more in a migration
2017-08-25 12:04:40 +02:00
Grzegorz Bizon
3eba43b62d
Adjust a range and a size in stages statuses migration
2017-08-23 14:48:26 +02:00
Grzegorz Bizon
13a15e7009
Use update_column_in_batches helper in stages migration
2017-07-31 12:23:04 +02:00
Grzegorz Bizon
bb67b4749b
Update version number of stages statuses migration
2017-07-11 14:31:04 +02:00