On Thu, Dec 10, 2009 at 10:03 PM, 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. > I think that if you have the possibility to use a database server (PostgreSQL, MySQL, etc), you should do it. I've only used SQLite3 on a desktop application in production mode, and it worked just fine, but I wouldn't rely on it for an application of the kind your describing here.
Just my 2 cents. Cheers! -- Leonardo Mateo. There's no place like ~ -- 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.
