if association is in "include" option, counter_cache field should be in "except" option, otherwise counter_cache field is multiplied by 2 and doesnt represent actual number of associated records (maybe should be mentioned in docs or managed automatically if possible)
Hi, thanks for the feedback! As it is part of the configuration of associations, I think I agree it should be managed automatically. Will have a look when I have the time. PRs are welcome too ;)
if association is in "include" option, counter_cache field should be in "except" option, otherwise counter_cache field is multiplied by 2 and doesnt represent actual number of associated records (maybe should be mentioned in docs or managed automatically if possible)