diff options
author | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2016-03-14 22:36:08 -0300 |
---|---|---|
committer | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2016-03-14 22:36:08 -0300 |
commit | 6ca9031ba3c389f71366c3e6abf069c6924c5acf (patch) | |
tree | 0dbfdcc64665a301b78966753e9a8f7e091a534f /rails.gemspec | |
parent | 4232f7ee427a510eb07e420f5883611bcb0abfae (diff) | |
download | rails-6ca9031ba3c389f71366c3e6abf069c6924c5acf.tar.gz rails-6ca9031ba3c389f71366c3e6abf069c6924c5acf.tar.bz2 rails-6ca9031ba3c389f71366c3e6abf069c6924c5acf.zip |
Creates development and test databases in db:migrate task
This reverts a334425caff9b2140d5e99fcfc2eb8c4ab10bdfa.
The main reason is that now the workflow is inconsistent when using
spring.
When using spring `RAILS_ENV` is always set, so only one database is
created.
This means that in development `bin/rake db:create` and `bundle exec
rake db:create` have different results.
It also breaks the `bin/setup` script since `bin/rake db:setup
db:test:prepare` will fail.
Diffstat (limited to 'rails.gemspec')
0 files changed, 0 insertions, 0 deletions