A counter_cache provides a reasonable way to speed up code which faults in a collection just to get the size.  In my experience, the most painful part is initializing the column with the first value.  Traditionally the Rails blogs use Ruby code to iterate through every instance, calculating the value by performing an individual query and saving the result.  It's much, much faster (and easier in many cases) to initialize the column value with a single query.  Imagine POSTS and COMMENTS tables where you want a COMMENTS_COUNT column to speed up the lookup of posts.comments.size. Here's the beef:

update posts, (select post_id, count(*) as the_count from comments group by post_id) as comm set posts.comments_count = comm.the_count where posts.id = comm.post_id;

Note the use of a temporary table to hold the intermediate, calculated size.  This has been tested in MySQL.  YMMV.

comments powered by Disqus