On 13 September 2012 22:20, Jeff Pritchard <li...@ruby-forum.com> wrote: > Colin Law wrote in post #1075905: >> On 13 September 2012 21:41, Jeff Pritchard <li...@ruby-forum.com> wrote: >>> db over from the old server, or if there will be a need for some sort of >>> a migration? >>> >>> Any info on what I'm up against there will be much appreciated. >> >> In that situation I would use mysqldump to get a dump of the db and >> create the new one from that. There may well be better ways however. >> >> Colin > > Thanks Colin! > > This is sort of: > binary data --> long list of SQL statements > long list of SQL statements --> binary data using new version of mySQL > > yes?
yes > > Is this primarily to solve any compatibility issues between versions of > mySqL rather than from rails 2.x to rails 3.x? Yes, rails should not care which version of mysql you are using. As a side note I use this as a way of backing up the database (by backing up the sql statements) as an emergency fallback in case the binary backup fails for some reason. I am not sure there is a good logical argument for this but it just seems like a good idea to have something one can actually read as a backup. Colin -- 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-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
