3.2.
Gabriel
On Thursday, February 9, 2012 10:09:38 AM UTC-8, tigrish wrote:
I'm seeing the same problem after having upgraded to rails 3.2 .
No custom serializer for me, just a regular serialized field.
Previous behaviour was to have the field automatically deserialized, but
instead I'm getting the serialized version.
--I'm seeing the same problem after having upgraded to rails 3.2 .
No custom serializer for me, just a regular serialized field.
Previous behaviour was to have the field automatically deserialized, but
instead I'm getting the serialized version.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/85iDW81V9y4J.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
