Actually it really would be a better way to go straight with SQL. Forget what I said about ORM :)
On Sat, Dec 6, 2008 at 5:22 AM, Steven Fines <[EMAIL PROTECTED]> wrote: > An even better solution would be to take advantage of mysql's selective > replication feature. It'll be more complicated to set up, but if you're > going to move a lot of rows on a regular basis and need the data moved > now(tm) it'd be the way to go. > If this is a one-off or once a year type task, I'd follow Mr. Bresnik's > advice and use straight SQL. > > > > On Fri, Dec 5, 2008 at 7:33 PM, John Bresnik <[EMAIL PROTECTED]> wrote: > >> You should straight sql for this.. basically an insert statement with an >> encapsulated select, doing with AR would be real expensive.. >> >> On Dec 5, 2008 1:38 PM, "liquid_rails" <[EMAIL PROTECTED]> wrote: >> >> >> Thanks, but I don't even know how to write the script or the code for >> moving the records. Do you know of any websites or books that could >> show me how to do this? >> Thanks! >> >> On Dec 5, 11:34 am, Phlip <[EMAIL PROTECTED]> wrote: > John Bresnik >> wrote: > > Put the code for m... >> >> >> >> > > > > -- Att, - Caike --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
