This project is archived and is in readonly mode.

#5085 ✓stale

Wrong message using "rake db:create"

Reported by MarcRic | July 11th, 2010 @ 12:53 PM

I have created a brand new Rails app.

Then, using the default SQLite database configuration, have tried to create a new database using "rake db:create".

The action performs nice, but send a wrong "already exists" message, where in fact it don't.

This way:

Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


E:>cd projects

E:\projects>cd newapp

E:\projects\newapp>rake db:create
(in E:/projects/newapp) db/development.sqlite3 already exists

E:\projects\newapp>gem list


actionmailer (2.3.6)
actionpack (2.3.6)
activerecord (2.3.6)
activeresource (2.3.6)
activesupport (2.3.6)
gem_plugin (0.2.3)
mongrel (1.1.6)
rack (1.1.0)
rails (2.3.6)
rake (0.8.7)
sqlite3-ruby (1.2.5)

E:\projects\newapp>ruby -v
ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]


Comments and changes to this ticket

  • Mike Riley

    Mike Riley July 29th, 2010 @ 09:21 PM

    • State changed from “new” to “open”
    • Importance changed from “” to “Low”


    I tried to replicate this, but was not able to do so. Can you ensure that this database does not already exist? The database if it is created will be in your Rails root folder in the db directory. When I created a new application it only created the following:

      create  db
      create  db/seeds.rb

    I tried this with Rails 3.0 rc 1 and Rails 2.3.8. I wasn't able to test this with Windows, but I can do some more work on this if you would like. Let me know if you see the development.sqlite3 when you create a new Rails app.

    Mike Riley

  • Santiago Pastorino

    Santiago Pastorino February 2nd, 2011 @ 04:34 PM

    • Tag changed from activerecord 3.0, rake to activerecord 30, rake

    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

    Santiago Pastorino February 2nd, 2011 @ 04:34 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=""></a>

People watching this ticket