When we started working on the merb stack, I didn't add an extension to default sqlite database.yml. Pretty quickly beta testers started complaining that it was a bit confusing and it would be more obvious to add an extension to the file.
As Cyril said, you don't need to set an extension to the file name. Merb ORM will pick up the file without a problem, however, having an extension will make browsing for the sqlite3 db files easier. What you need to understand, and maybe that's the piece you didn't quite get, is that sqlite3 uses standalone files to store your dbs. Other RDBMS like MySQL, Postgres etc... use a more complex storing mechanism to which you don't really have access. That's another reason why sqlite3 is the default db mechanism, you don't need to have anything setup or running, apart from sqlite3 installed. I hope this helps, - Matt On Sun, Dec 14, 2008 at 12:33 AM, Cyril Mougel <[email protected]>wrote: > > Eeby wrote: > > In the initially generated database.yml, why does it say "database: > > sample_development.db" not "database: sample_development"? > > > > What's the ".db" for? Does it refer to another config file that I need > > to set up somewhere? > > > it's better to have a file extension in your SQLITE file. You can delete > this end. All works after. > > -- > Cyril Mougel > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
