serialized :attribute fails when specified in STI subclass
Reported by Wes | May 15th, 2008 @ 10:00 PM
When using STI, if a subclass specifies that an attribute is to be serialized, and that attribute was not specified as serialized in the base class, serialization of the attribute fails.
This bug will only occur in production, not in development mode due to the class reloading in development mode.
class Droid < ActiveRecord::Base
end
class R2D2 < Droid
serialize :secret_message
end
If the R2D2 class is loaded in production after the Droid class is loaded, then the serialization of the secret_message attribute will fail.
Patch and tests attached.
Comments and changes to this ticket
-
Pratik May 15th, 2008 @ 10:03 PM
- → Assigned user changed from “” to “Michael Koziarski”
-
Joshua Peek August 20th, 2008 @ 01:52 AM
- → Tag changed from “” to “activerecord bug patch serialized tested”
- → State changed from “new” to “stale”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
Michael Koziarski
Les Hill