Tuesday, January 28, 2014
Hi Jones,
Its so kind of you. Thanks for your suggestion.
On Tuesday, January 28, 2014 11:10:02 PM UTC+5:30, Matt Jones wrote:
-- Its so kind of you. Thanks for your suggestion.
On Tuesday, January 28, 2014 11:10:02 PM UTC+5:30, Matt Jones wrote:
On Friday, 24 January 2014 00:44:22 UTC-5, Anand Vignesh wrote: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 applicationno _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. :)
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
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/16c9e591-bb8f-49aa-adc5-1ccc81dd6a9c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment