diff options
| author | Michael Duchemin <msducheminjr@users.noreply.github.com> | 2019-01-27 00:23:47 -0500 |
|---|---|---|
| committer | Michael Duchemin <msducheminjr@users.noreply.github.com> | 2019-02-09 15:34:13 -0500 |
| commit | 93d2090011b5ccab504b8aeabf6a95b23193a689 (patch) | |
| tree | 8693a081352744a2c770d3c2b072f910975cbfb2 /guides/rails_guides | |
| parent | ea0eaced55465ce8054cf54ff583d75272bd8505 (diff) | |
| download | rails-93d2090011b5ccab504b8aeabf6a95b23193a689.tar.gz rails-93d2090011b5ccab504b8aeabf6a95b23193a689.tar.bz2 rails-93d2090011b5ccab504b8aeabf6a95b23193a689.zip | |
Add class option timestamps to migration generator
Fixes GH#28706. Now rails g migration create_users and rails g model User have the same behavior for timestamps since they implement the same migration template. The expected behavior is that this create table migration will create the table with timestamps unless you pass --no-timestamps or --skip-timestamps to the generator. The expected migration should match what you get when you use the model generator. Using the migration generator, which doesn't have a class_option for timestamps would cause them to not be added to the migration file. Now the migration behavior of the migration generator, create_table only, is aligned with the migration behavior of the model generator. Also modified relevant example of ActiveRecord Migrations Guide.
Diffstat (limited to 'guides/rails_guides')
0 files changed, 0 insertions, 0 deletions