kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Merge pull request #34222 from bogdanvlviv/unify-changelog-entries

Browse source 
Unify changelog entries related to `database` option of Rails generators [ci skip]
This commit is contained in:
Rafael França 2018-10-22 16:49:31 -04:00 committed by GitHub
commit e853acb9b4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
railties/CHANGELOG.md
View file

@ -17,34 +17,18 @@
*DHH*, *Lachlan Sylvester*
* Refactors `migrations_paths` command option in generators
to `database` (aliased as `db`). Now, the migrations paths
will be read from the specified database configuration in the
current environment.
* Add `database` (aliased as `db`) option to model generator to allow
setting the database. This is useful for applications that use
multiple databases and put migrations per database in their own directories.
```
bin/rails g model Chair brand:string --database=kingston
invoke active_record
create db/kingston_migrate/20180830151055_create_chairs.rb
```
`--database` can be used with the migration, model, and scaffold generators.
*Gannon McGibbon*
* Adds an option to the model generator to allow setting the
migrations paths for that migration. This is useful for
applications that use multiple databases and put migrations
per database in their own directories.
```
bin/rails g model Room capacity:integer --migrations-paths=db/kingston_migrate
bin/rails g model Room capacity:integer --database=kingston
invoke active_record
create db/kingston_migrate/20180830151055_create_rooms.rb
```
Because rails scaffolding uses the model generator, you can
also specify migrations paths with the scaffold generator.
also specify a database with the scaffold generator.
*Gannon McGibbon*
@ -72,15 +56,15 @@
*Yoshiyuki Kinjo*
* Add `--migrations_paths` option to migration generator.
* Add `database` (aliased as `db`) option to migration generator.
If you're using multiple databases and have a folder for each database
for migrations (ex db/migrate and db/new_db_migrate) you can now pass the
`--migrations_paths` option to the generator to make sure the the migration
`--database` option to the generator to make sure the the migration
is inserted into the correct folder.
```
rails g migration CreateHouses --migrations_paths=db/kingston_migrate
rails g migration CreateHouses --database=kingston
invoke active_record
create db/kingston_migrate/20180830151055_create_houses.rb
```