Perhaps you could take a look at the sqlite page with the title. Appropriate Uses for SQLite - http://www.sqlite.org/whentouse.html
I'm not a massively experienced developer but from you description the app won't be getting lots of reads or writes over a short period of time so I think it would be worth trying. Regards, James. On Fri, Dec 11, 2009 at 11:03 AM, Steven Elliott Jr < [email protected]> wrote: > Hello, > > I am writing an intranet application that is to be used in an > evironment of about 50 users. It's basically an HR app that tracks > employee's benefits, sick days, vacations, etc. > > I've developed using sqlite3 and it's about time to deploy. I don't > see a ton of multiple writes happening at once so I'm wondering if > it's worth it to use sqlite3 as the production database as well. Has > anyone ever used sqlite3 as a production db? If so what blew up? It's > not a big deal to use MySQL just wondering. > > Thanks, > Steve > > -- > > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
