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 |
|
Lin Jen-Shin
|
4a03032660
|
Fix rolling back for MySQL
|
2017-04-06 14:41:27 +08:00 |
|
Rydkin Maxim
|
b9f7d4b45e
|
split up migrations
|
2017-04-04 21:11:25 +03:00 |
|
Rydkin Maxim
|
a0de26f2c4
|
fix migration error
|
2017-04-04 21:11:25 +03:00 |
|
Rydkin Maxim
|
4f748f74bc
|
replace on_delete in migration with database type related expression
|
2017-04-04 21:11:25 +03:00 |
|
Rydkin Maxim
|
effcbaf372
|
fix on_delete
|
2017-04-04 21:11:24 +03:00 |
|
Rydkin Maxim
|
a4d08e6bab
|
rename `auto_canceled_by` and add foreign key
|
2017-04-04 21:11:24 +03:00 |