Hi there, I'm Vignesh developer @ Rails application. I was now getting an issue while I'm migrating my existing application with rails '3.2.13' into rails '4.1.beta1' . This was my issue while i m signing in into my application no _dump_data is defined for class Mysql2::Result So if anyone could have some idea about the issue. Please share your ideas and it may be helpful for fixing it. :) Thanks, Vignesh.
on 2014-01-24 09:14
on 2014-01-24 15:23
you might do better with the Ruby on Rails: Core group...
on 2014-01-28 07:38
Hey Rick, I'm new to ROR thats y i'm facing many challenges..
on 2014-01-28 18:41
On Friday, 24 January 2014 00:44:22 UTC-5, Anand Vignesh wrote: > > > So if anyone could have some idea about the issue. Please share your ideas > and it may be helpful for fixing it. :) > > > The Mysql2::Result class is a thin wrapper over the underlying C interface - in particular, it can do things like on-demand streaming of rows from the database. It's not Marshal-able because most of the state doesn't live in Ruby code. As noted in the issue on the Mysql2 gem (https://github.com/brianmario/mysql2/issues/275), the workaround is to convert the Mysql2::Result instance to a hash or an array (fetching all the desired rows) *before* caching it. --Matt Jones
on 2014-01-29 06:17
Hi Jones, Its so kind of you. Thanks for your suggestion.