This project is archived and is in readonly mode.
db:abort_if_pending_migrations fails with exception if development database hasn't been created
Reported by Josh Nichols | June 19th, 2010 @ 08:46 PM
I just started up a fresh rails 3.0.0.beta4 project and tried running the default rake task, before having created a database or really any code. It failed with this message:
$ rake -s
Errors running test:units!
Next, I tried running the test:units directly:
$ rake -s test:units
rake aborted!
Unknown database 'myapp_development'
(See full trace by running task with --trace)
I'm familiar enough with rails to know that I just need to
create the database, ie using @rake db:create@, but it might not be
so clear to everyone. Maybe we could do a begin/rescue here, and
indicate that rake db:create
needs to be run?
Comments and changes to this ticket
-
Santiago Pastorino February 2nd, 2011 @ 05:02 PM
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 05:02 PM
- State changed from open to stale
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>