56296f1eda
Remove rails4 specific code
2018-12-16 10:48:41 +01:00
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
85a7e0813e
Support rails5 in postgres indexes function and fix some migrations
2018-06-05 08:06:35 +02:00
98bb435f42
Enable RuboCop for migrations
...
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.
2016-06-09 16:05:25 +01:00
dcd54f6345
Attempt to create pg_trgm extension in migration for test/dev environments
...
Closes #15210
2016-04-20 20:59:01 -07:00
67143e25a2
More detailed trigram migration error message
...
This explains the user what they need to run and where to go in case
they want to learn more about "CREATE EXTENSION".
2016-03-11 15:26:32 -05:00
d24ee2a206
Added trigram indexes for various searched columns
...
This allows the LIKE condition to use an index. Without a GIN + trigram
index LIKE queries using a wildcard at the start _won't_ use an index
and instead perform a sequence scan.
2016-03-11 15:25:21 -05:00
Jasper Maes