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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Thu, Dec 10, 2009 at 10:03 PM, Steven Elliott Jr <stevenelliott0623-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
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 < stevenelliott0623-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<rubyonrails-talk%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> > . > 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Ya, guess I should have read that first. I''m going to give it a try to see how it stands up. Worse comes to worse I can always move everything to MySQL. Thanks. Steve On Dec 10, 2009, at 8:42 PM, James Sullivan <zaphodharkonnen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> 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 <stevenelliott0623-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org > > 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 rubyonrails- > talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > . > 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 rubyonrails- > talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > . > 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.