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 |
|
Z.J. van de Weg
|
083c0e28f7
|
Support empty PG database too
First check if there is a result on the migration, else there is
nothing to do
|
2016-09-06 12:13:45 +02:00 |
|
Z.J. van de Weg
|
5204911f61
|
Don't fail on an empty database
|
2016-09-05 19:53:38 +02:00 |
|
Z.J. van de Weg
|
e683eecdd9
|
Support MySQL too, when removing gitorious from import_sources
|
2016-09-05 19:15:22 +02:00 |
|
Z.J. van de Weg
|
2246218cc0
|
Remove gitorious from import_sources on ApplicationSetting model
|
2016-09-05 19:15:22 +02:00 |