Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Intervene on change_table as well as create_table | Matthew Draper | 2016-01-30 | 1 | -0/+13 |
| | |||||
* | Pare back default `index` option for the migration generator | Prathamesh Sonpatki | 2016-01-24 | 1 | -0/+12 |
| | | | | | | | | | | - Using `references` or `belongs_to` in migrations will always add index for the referenced column by default, without adding `index:true` option to generated migration file. - Users can opt out of this by passing `index: false`. - Legacy migrations won't be affected by this change. They will continue to run as they were before. - Fixes #18146 | ||||
* | fix remove_index for postgresql when running legacy migrations | Lachlan Sylvester | 2016-01-06 | 1 | -2/+3 |
| | |||||
* | Support removing custom-names indexes when only specifying column names | Grey Baker | 2015-12-15 | 1 | -0/+25 |
| | |||||
* | Ignore index name in `index_exists?` when not passed a name to check for | Grey Baker | 2015-12-15 | 1 | -0/+11 |
| | |||||
* | In 4.2 migrations, `timestamps` defaulted to `null: true` | Matthew Draper | 2015-12-15 | 1 | -0/+24 |
| | | | | | .. it also showed a deprecation warning, but we obviously needn't retain that. | ||||
* | Add migration versioning via Migration subclasses | Matthew Draper | 2015-12-15 | 1 | -0/+30 |