On 14 September 2012 15:17, Jeff Pritchard <li...@ruby-forum.com> wrote: > Colin Law wrote in post #1075952: >> On 13 September 2012 22:20, Jeff Pritchard <li...@ruby-forum.com> wrote: >>>> 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. ... >> Colin > > Thanks again Colin. I'm left still with one question though...are there > any specific differences in Rails from 2.x to 3.x which result in > important db content differences and non-compatible databases? (not to > do with the other parts of the environment, but specifically the way > that rails uses the database).
Not that I can think of, but you will no doubt find out as you do the upgrade :) If you google for how to upgrade from 2 to 3 you will find numerous guides on how to do that. Look through those to see if there is any reference to database differences. 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.
