diff options
author | Jon Leighton <j@jonathanleighton.com> | 2011-09-11 14:48:40 +0100 |
---|---|---|
committer | Jon Leighton <j@jonathanleighton.com> | 2011-09-13 00:01:58 +0100 |
commit | eecfa84a9065da2b1bd1e02f37e8653a2825c624 (patch) | |
tree | 103ae42eb5c8f6206a5eac7b731307b3348dadb7 /activerecord/test/fixtures/fk_test_has_pk.yml | |
parent | 50d395f96ea05da1e02459688e94bff5872c307b (diff) | |
download | rails-eecfa84a9065da2b1bd1e02f37e8653a2825c624.tar.gz rails-eecfa84a9065da2b1bd1e02f37e8653a2825c624.tar.bz2 rails-eecfa84a9065da2b1bd1e02f37e8653a2825c624.zip |
Always generate attribute methods on the base class.
This fixes a situation I encountered where a subclass would cache the
name of a generated attribute method in @_defined_class_methods. Then,
when the superclass has it's attribute methods undefined, the subclass
would always have to dispatch through method_missing, because the
presence of the attribute in @_defined_class_methods would mean that it
is never generated again, even if undefine_attribute_methods is called
on the subclass.
There various other confusing edge cases like this. STI classes share
columns, so let's just keep all the attribute method generation state
isolated to the base class.
Diffstat (limited to 'activerecord/test/fixtures/fk_test_has_pk.yml')
0 files changed, 0 insertions, 0 deletions