Colin Law wrote: > On 17 June 2010 22:22, Marnen Laibow-Koser <[email protected]> wrote: >> Toby Rodwell wrote: >>... >> If you don't have control of the database, you should not be doing the >> project. �Really. >> > > I don't think this is a valid general point. There are often > situations involving a legacy database where it is not feasible to > change the database but where RoR makes sense for additional > functionality, particularly web access. >
Rails can work with legacy DBs to a certain extent. It wants its DBs set up a certain way, though, and that's where the developer needing to have control of the DB comes in. It's particularly necessary if the OP wants to make the transition to nested sets, since you can't do that without storing the left and right values. > Colin Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [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.
