This project is archived and is in readonly mode.
rake db:create does not do what the description says
Reported by Kane | August 15th, 2010 @ 12:51 AM
commit
http://github.com/rails/rails/commit/fbdef7aafe753d2375b16c5dcf70a4...
by Mikel Lindsaar changed the behaviour of rake db:create to also
generate the test database if in dev env.
this was documented in the task description. I could not find any
ticket to this change.
commit
http://github.com/rails/rails/commit/983815632cc1d316c7c803a47be28f...
by DHH
changed the task description so this behaviour is no longer
described properly.
Create the database from config/database.yml for the current Rails.env (use db:create:all to create all dbs in the config)
my question is why was the behaviour changed in the first
place?
Additionally creating the test database if in development env seems
strange to me, i cant see the reason. And why was this behaviour
obscurified afterwards?
Comments and changes to this ticket
-
x0f August 20th, 2010 @ 05:15 PM
- Assigned user set to DHH
Seems like a documentation error to me. It's sad that DHH made this mistake in an afford to simplify the rake-task-jitter, thus leading to more readable system, but one which doesn't reflect the actual functionality.
How ever, I also don't like the way the behaviour was changed, even if it supports a more 'agile' programming style. A more suitable solution would be another development-specific rake task, which addresses this particular problem.
-
Andrew White August 23rd, 2010 @ 05:15 PM
- State changed from new to duplicate
- Assigned user cleared.
- Importance changed from to Low
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Referenced by
- 5313 Rake tasks db:create and db:drop are not consistent in behaviour i encountered this too, see #5382