Bob T. wrote in post #961705: > Regarding migrations - Please quote when replying.
> > We use Oracle, MySql , PHP, Perl/DBI and are just considering using RoR. > > If we choose to develop some things in RoR, it will have to learn to get > along with the code and the database tables we already have. And so it can. But you should dump the schema into the schema file as I already suggested. > > If you use only one technology, I understand why you would recommend > using that technology exclusively. Personally, I don't believe in > getting locked into a particular technology. Thats my choice. I don't either. But while you're developing in Rails, you should use Rails migrations. It's not great practice to have multiple applications touching the same DB anyway. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- 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.
