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 |
Jasper Maes
|
85a7e0813e
|
Support rails5 in postgres indexes function and fix some migrations
|
2018-06-05 08:06:35 +02:00 |
Lin Jen-Shin
|
6ff162cfd9
|
Add back project_id index for MySQL if reverting
|
2017-06-23 19:09:23 +08:00 |
Lin Jen-Shin
|
d34e87818c
|
Remove old project_id index and make sure mysql work
|
2017-06-23 18:09:22 +08:00 |
Lin Jen-Shin
|
5eb4a47204
|
We cannot delete the index for MySQL, because fk
foreign key, I mean.
|
2017-06-23 00:20:44 +08:00 |
Lin Jen-Shin
|
5725b3769f
|
Remove duplicated records and add unique constraint
|
2017-06-22 15:54:23 +00:00 |