On 10/02/2008, at 3:27 PM, Dave Amos wrote: > Shawn Balestracci wrote: >> The database is stored in its own file (named in your database.yml) >> >> To access it, on the commandline: >> sqlite3 filename >> on the server and directory where it is located (or use the full >> path). The database will most likely be in the RAILS_ROOT directory >> of your application. > > Okay, yeah, that makes sense. I did this: > > sqlite3 db/production.sqlite3 > > which was the file that my database.yml file pointed me to. When I > ran: > > .databases > > it gave me: > > seq name file > --- --------------- > ---------------------------------------------------------- > 0 main > /home/dave/public_html/statesidesoccer.net/releases/200802 > 1 temp /var/tmp/etilqs_u8MlqQJVLCpUUa1 > > I don't know what that means... I assume "main" is the db I want, > but I > don't know how to select it.
Hi Dave Each sqlite file is a database - in this case, db/production.sqlite3 - there's not multiple databases within it (I'm not sure if that's possible with sqlite). So, now that db/production.sqlite3 exists, you should be able to run your migrations on it: rake db:migrate RAILS_ENV=production Then the .tables command in sqlite should show all your tables in that file. Cheers -- Pat e: [EMAIL PROTECTED] || m: 0413 273 337 w: http://freelancing-gods.com || p: 03 9386 0928 discworld: http://ausdwcon.org || skype: patallan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
