aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/rails/generators/active_record.rb
Commit message (Collapse)AuthorAgeFilesLines
* Use frozen-string-literal in ActiveRecordKir Shatrov2017-07-191-0/+2
|
* Revert "Merge pull request #29540 from kirs/rubocop-frozen-string"Matthew Draper2017-07-021-1/+0
| | | | | This reverts commit 3420a14590c0e6915d8b6c242887f74adb4120f9, reversing changes made to afb66a5a598ce4ac74ad84b125a5abf046dcf5aa.
* Enforce frozen string in RubocopKir Shatrov2017-07-011-0/+1
|
* Define path with __dir__bogdanvlviv2017-05-231-1/+1
| | | | | | ".. with __dir__ we can restore order in the Universe." - by @fxn Related to 5b8738c2df003a96f0e490c43559747618d10f5f
* applies new string literal convention in activerecord/libXavier Noria2016-08-061-4/+4
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Make `.next_migration_number` reusable for third party AR generators.Yves Senn2013-09-301-8/+2
|
* nodoc AR::Generators [ci skip]Francesco Rodriguez2012-10-201-3/+3
|
* Remove unused implementation of next_migration_numberMarcelo Silveira2012-02-231-2/+0
|
* Implemented ActiveRecord::Migrations#copy based on James Adam's ideaPiotr Sarnacki2010-09-031-0/+6
| | | | | | | | | | | | | | | ActiveRecord::Migration#copy allows to copy migrations from one place to another, changing migrations versions and adding scope to filename. For example: ActiveRecord::Migration.copy("db/migrate", :blog_engine => "vendor/gems/blog/db/migrate") will copy all migrations from vendor/gems/blog/db/migrate to db/migrate with such format: Versions of copied migrations will be reversioned to be appended after migrations that already exists in db/migrate
* split out active_record migration logic so others can easily reuse [#5389 ↵Jack Dempsey2010-09-011-10/+2
| | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Update generators to use thor 0.13.6 with simpler source_root handling.José Valim2010-04-301-7/+3
|
* Make the migration generator handle pre-existing migrations with the same ↵Phil Smith2010-04-191-2/+3
| | | | | | | | | | timestamp. In the event a migration already exists with that number, the new migration's timestamp will be incremented by 1. [#4412 state:resolved] Signed-off-by: Michael Koziarski <michael@koziarski.com>
* Load generators from both lib/rails/generators and lib/generators. Using the ↵José Valim2010-03-231-0/+30
former since it's less obstrusive.