Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Extract sql fragment generators for alter table from PostgreSQL adapter | Dinah Shi | 2017-12-02 | 1 | -0/+17 |
| | |||||
* | Should test `LegacyPrimaryKeyTest` to both `V5_0` and `V4_2` | Ryuta Kamizono | 2017-10-18 | 1 | -15/+34 |
| | |||||
* | compatibility - use int instead of bigint | pavel | 2017-10-18 | 1 | -0/+3 |
| | |||||
* | Adding legacy primary key should be compatible | Ryuta Kamizono | 2017-09-23 | 1 | -0/+51 |
| | | | | | | | Currently implicit legacy primary key is compatible, but adding explicit legacy primary key is not compatible. It should also be fixed. Fixes #30664. | ||||
* | make create_join_table compatible. | Yuki Masutomi | 2017-09-20 | 1 | -0/+30 |
| | |||||
* | Use frozen-string-literal in ActiveRecord | Kir Shatrov | 2017-07-19 | 1 | -0/+2 |
| | |||||
* | Revert "Merge pull request #29540 from kirs/rubocop-frozen-string" | Matthew Draper | 2017-07-02 | 1 | -1/+0 |
| | | | | | This reverts commit 3420a14590c0e6915d8b6c242887f74adb4120f9, reversing changes made to afb66a5a598ce4ac74ad84b125a5abf046dcf5aa. | ||||
* | Enforce frozen string in Rubocop | Kir Shatrov | 2017-07-01 | 1 | -0/+1 |
| | |||||
* | Add test for backward compatibility when using change_table | Koichi ITO | 2017-06-13 | 1 | -0/+15 |
| | |||||
* | `primary_key` and `references` columns should be identical type | Ryuta Kamizono | 2017-02-07 | 1 | -0/+4 |
| | | | | | | | | Follow up to #26266. The default type of `primary_key` and `references` were changed to `bigint` since #26266. But legacy migration and sqlite3 adapter should keep its previous behavior. | ||||
* | Restore the behaviour of the compatibility layer for integer-like PKs | Ryuta Kamizono | 2017-02-04 | 1 | -0/+104 |
| | | | | | | | | | | | | | | | | | | | | | The PR #27384 changed migration compatibility behaviour. ```ruby class CreateMasterData < ActiveRecord::Migration[5.0] def change create_table :master_data, id: :integer do |t| t.string :name end end end ``` Previously this migration created non-autoincremental primary key expected. But after the PR, the primary key changed to autoincremental, it is unexpected. This change restores the behaviour of the compatibility layer. | ||||
* | show correct class name in migration inherited directly error | yuuji.yaginuma | 2017-01-24 | 1 | -2/+3 |
| | | | | Follow up to 249f71a | ||||
* | Raises when `ActiveRecord::Migration` is inherited directly. | Rafael Mendonça França | 2016-12-29 | 1 | -12/+6 |
| | |||||
* | modernizes hash syntax in activerecord | Xavier Noria | 2016-08-06 | 1 | -3/+3 |
| | |||||
* | applies new string literal convention in activerecord/test | Xavier Noria | 2016-08-06 | 1 | -5/+5 |
| | | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default. | ||||
* | Fix random failures of tests on Travis | Prathamesh Sonpatki | 2016-02-12 | 1 | -1/+1 |
| | | | | | | | | | | - Tests on Travis are randomly failing because schema_migrations table does not exist in teardown block. - Also checked that all other places where we have used `ActiveRecord::SchemaMigration.delete_all` we have rescued it, so used it here also. This failure was not specifically related to the test added in this PR but to overall compatibility migration tests, so adding as separate commit. | ||||
* | Correctly show deprecation warning for incompatible migrations | Prathamesh Sonpatki | 2016-02-12 | 1 | -0/+12 |
| | |||||
* | Added test for backward compatibility of null constraints on timestamp columns | Prathamesh Sonpatki | 2016-01-31 | 1 | -0/+30 |
| | |||||
* | Pare back default `index` option for the migration generator | Prathamesh Sonpatki | 2016-01-24 | 1 | -0/+18 |
| | | | | | | | | | | - 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 | -0/+16 |
| | |||||
* | Support removing custom-names indexes when only specifying column names | Grey Baker | 2015-12-15 | 1 | -0/+42 |