Leo.liang

@mrfoto That is a valid point, but in my project, the actual model I have the count and size problem is a model call Claim. And I use job_seekers.count to calculate claim amount, and job_seekers.count will only be used once and not called in other places, so it is a bit overkill to create countercachecolumn for job_seekers.count in my case. If I need to call job_seekers.count more than once outside Claim model, I will use counter_cache column for sure

Cheers