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
b95da565cd
Enable rubocop for db/**/* and ee/db/**/*
2018-07-25 17:47:12 +08:00
c914883a2b
Shortcut concurrent foreign key creation if already exists.
...
Closes #43887 .
2018-03-20 18:44:00 +01:00
5f35ea146a
Fix concurrency issue with migration for user_interacted_projects table.
...
The concurrency issue originates from inserts on
`user_interacted_projects` from the app while running the post-deploy
migration.
This change comes with a strategy to lock the table while removing
duplicates and creating the unique index (and similar for FK
constraints).
Also, we'll have a non-unique index until the post-deploy migration is
finished to speed up queries during that time.
Closes #44205 .
2018-03-14 17:51:47 +01:00
8e668076a9
Improve robustness of migration.
2018-03-06 12:53:15 +01:00
8a7cd25d08
For MySQL, foreign keys are dependent on index.
2018-03-06 12:53:14 +01:00
43b74afd86
Rename to UserInteractedProjects.
...
This is to avoid a mix-up with the existing concept of 'user
contributions'. See `User#contributed_projects` or
`Event#contributions`.
2018-03-06 12:53:14 +01:00
Jan Provaznik