giorgio wrote in post #968193: > Thanks for that idea Marnen, > > I will take a look at Foreigner.. > > I think I would still have problems importing one database into the > other ... > Say I import "Clients" and all the ids get updated I would need to > update all the client_id values on say the adresses table.... but the > addresses table may not be imported yet so would not cascade update. > > I think you are saying - Change all the primary keys on one of the > databases first and then do the merge and the keys will be in mutually > exclusive ranges..
Right. > I guess I would then possibly need to reset the sequences on the DB.. Yes. > > Whichever way I look has drawbacks! > How is resetting the sequences a big drawback? It's easy and you'll only need to do it once per DB. > Cheers > George Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] 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 [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.
