Robert Pankowecki wrote: > On Sep 19, 1:46�am, Marnen Laibow-Koser <li...@ruby-forum.com> wrote: >> Don't do that. �I saw the other thread, and I think you were given bad >> advice. �You almost always want one big DB for the whole thing. �It's >> usually easier to deal with. > > Any reason why it is wrong to do that ? Why is it easier in your > opinion?
A bunch of reasons. Deployment is easier since you don't have to maintain several DBs; Rails doesn't have to choose a DB; it's easier to analyze everyone's data together (which may often be necessary) if it's all in one DB; it may be more efficient. > My idea to split into multplie databases was just and idea. > Not an advice :-) > > Robert Pankowecki Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org Sent from my iPhone -- Posted via http://www.ruby-forum.com/. -- 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-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
