Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Squash old migrations | Nick Thomas | 2019-07-02 | 1 | -37/+0 |
| | | | | Use the `squasher` gem to squash migrations older than the start of 2018 | ||||
* | Add version 4.2 to all existing migrationsjprovazn-versioned-migrations | Jan Provaznik | 2018-11-22 | 1 | -1/+1 |
| | | | | | | | | | 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 | ||||
* | Adding NULL:false constraint with change_column_null instead of change_columnfix_set_null_false_migration | Valery Sizov | 2017-05-18 | 1 | -4/+4 |
| | |||||
* | Improve migration for Multipple issue assignee feature | Valery Sizov | 2017-05-16 | 1 | -0/+37 |