I read through the pull request
(Deprecate `serialized_attributes` without replacement by sgrif · Pull Request #15704 · rails/rails · GitHub)
of the deprecation of serialized_attributes
. I was wondering what I
should do in the future. The PR mentions using polymorphism, however,
what
should I use when the serialization does not represent a database
entity.
I understand that this blob concept violates first normal form anyway,
maybe part of the reason for the deprecation, not sure though.
On Thursday, July 23, 2015 at 3:03:19 PM UTC+1, Carson Reinke wrote:
I read through the pull request (Deprecate `serialized_attributes` without replacement by sgrif · Pull Request #15704 · rails/rails · GitHub)
of the deprecation ofserialized_attributes
. I was wondering what I
should do in the future. The PR mentions using polymorphism, however, what
should I use when the serialization does not represent a database entity.
I understand that this blob concept violates first normal form anyway,
maybe part of the reason for the deprecation, not sure though.
Hi,
Do you realise that it’s not serialize
and the general concept of
serialized_attributes that are deprecated, but only the method called
serialized_attributes that returns the list of serialized attributes ?
Fred
Ha! Ok, yes I see that now. Thank you!