diff options
author | Sean Griffin <sean@thoughtbot.com> | 2015-01-30 14:03:36 -0700 |
---|---|---|
committer | Sean Griffin <sean@thoughtbot.com> | 2015-01-31 19:42:38 -0700 |
commit | 70ac072976c8cc6f013f0df3777e54ccae3f4f8c (patch) | |
tree | 7a9d376fa4b2694c9b214da3cb8205ca1bcb3406 /activerecord/lib/active_record/querying.rb | |
parent | e2ccfebab4fd37603546998df2ee57b8bb07c168 (diff) | |
download | rails-70ac072976c8cc6f013f0df3777e54ccae3f4f8c.tar.gz rails-70ac072976c8cc6f013f0df3777e54ccae3f4f8c.tar.bz2 rails-70ac072976c8cc6f013f0df3777e54ccae3f4f8c.zip |
Attribute assignment and type casting has nothing to do with columns
It's finally finished!!!!!!! The reason the Attributes API was kept
private in 4.2 was due to some publicly visible implementation details.
It was previously implemented by overloading `columns` and
`columns_hash`, to make them return column objects which were modified
with the attribute information.
This meant that those methods LIED! We didn't change the database
schema. We changed the attribute information on the class. That is
wrong! It should be the other way around, where schema loading just
calls the attributes API for you. And now it does!
Yes, this means that there is nothing that happens in automatic schema
loading that you couldn't manually do yourself. (There's still some
funky cases where we hit the connection adapter that I need to handle,
before we can turn off automatic schema detection entirely.)
There were a few weird test failures caused by this that had to be
fixed. The main source came from the fact that the attribute methods are
now defined in terms of `attribute_names`, which has a clause like
`return [] unless table_exists?`. I don't *think* this is an issue,
since the only place this caused failures were in a fake adapter which
didn't override `table_exists?`.
Additionally, there were a few cases where tests were failing because a
migration was run, but the model was not reloaded. I'm not sure why
these started failing from this change, I might need to clear an
additional cache in `reload_schema_from_cache`. Again, since this is not
normal usage, and it's expected that `reset_column_information` will be
called after the table is modified, I don't think it's a problem.
Still, test failures that were unrelated to the change are worrying, and
I need to dig into them further.
Finally, I spent a lot of time debugging issues with the mutex used in
`define_attribute_methods`. I think we can just remove that method
entirely, and define the attribute methods *manually* in the call to
`define_attribute`, which would simplify the code *tremendously*.
Ok. now to make this damn thing public, and work on moving it up to
Active Model.
Diffstat (limited to 'activerecord/lib/active_record/querying.rb')
0 files changed, 0 insertions, 0 deletions