Can't create sqlite3 db

Rails
1

I’m running my rails environment in cygwin.

I have the older 1.2.6 rails.

I installed sqlite3 with their online installer (sqlite 3.5.1)

when I create a db with the command: sqlite3 test.db

I do no get a db, I just goes to the sqlite command prompt.

Am I creating the db wrong? I’m on version sqlite3 3.5.1 or is my
sqlite3 not installed correctly.

What is the optimal sqlite3 version?

2

It should automatically create the DB for you in your rails app.

On Jan 15, 2008 6:04 PM, Feng T. [email protected]
wrote:

Am I creating the db wrong? I’m on version sqlite3 3.5.1 or is my
sqlite3 not installed correctly.

What is the optimal sqlite3 version?

Posted via http://www.ruby-forum.com/.

–
Ryan B.

Feel free to add me to MSN and/or GTalk as this email.

3

So I do not need to manually create the db? It will autogen for
me when I set it in my yaml?

4

No, when you rake db:migrate
DaveP

On Jan 15, 5:56 pm, Feng T. [email protected]

5

Exactly.

Nicolai

6

Nicolai Reuschling wrote:

Exactly.

Nicolai

where exactly are the databases saved at when you migrate?

7

You are correct.

It takes a second to wrap your mind around exactly what SQLite is
doing, but I’ve been happy to use it for all of my development stuff
so far.

8

in /db, I believe.

On Jan 16, 9:11 pm, Feng T. [email protected]

9

did u try creating your app like ruby <name_of_application>
–database=sqlite3
also check your database.yml file in the config directory for correct
adapters.

Cheers
On Jan 17, 2008 8:12 AM, Bobnation [email protected] wrote:

On Jan 16, 9:11 pm, Feng T. [email protected]

–
Cheers,
Vaibhav
Helping Laymen become Technology Enthusiasts at

10

On Thu, 17 Jan 2008 09:17:24 +0530, Vaibhav Pandey wrote:

did u try creating your app like ruby <name_of_application>
–database=sqlite3
also check your database.yml file in the config directory for correct
adapters.

Ditto.

rails foo --database=sqlite3

the above command will create a rails project and db in one go. If it
doesn’t, then there’s something wrong with the setup. (The db file is,
IIRC, named foo_development.db or similar.)

-Thufir