HasManyAssociation: moved half of counter cache code to reflection

Current implementation has a lot of utility methods that accept
reflection call a lot of methods on it and exit.

E.g. has_counter_cache?(reflection)

It causes confusion and inability to cache result of the method even
through it always returns the same result for the same reflection
object.
It can be done easier without access to the association context
by moving code into reflection itself.

e.g. reflection.has_counter_cache?

Reflection is less complex object than association so moving code there
automatically makes it simplier to understand.

0 files changed, 0 insertions, 0 deletions