gjolund
commented
10 years ago this makes a lot of sense. Initially I thought it would be better to use the @getGuid() method to make the count collection specific to a table, but tying it to the query allows it to be reused. smart :)
Also, I'll revert the changes I made storing everything in a client collection.
I figured out why this is happening. It is because there is only a single count established for each publication and it doesn't get updated for new datatables using the same collection that subscribe to it. Here is a possible solution for tracking unique counters for each subscription. Tying it to the base_query seemed like a good solution to me for keeping to total number of tracked counters to a minimum.