How does the :countish paginator determine cache keys?

[JasonBarnabe]

https://ddnexus.github.io/pagy/toolbox/paginators/countish/

:countish is an OFFSET paginator that memoizes the result of the COUNT query, running it only once per collection (instead of once per page), and optionally recounting it when it's stale.

What is the cache key used here? I expect that for ActiveRecord collections, Discussion.where(user_id: 1) and Discussion.where(user_id: 2) would have different cache keys. I'm not sure how other types of collections like searchkick results would work. Can this be clarified in the documentation?

[ddnexus]

Can this be clarified in the documentation?

No, you just... have faith! 🤣

Ok, I can add one more sentence in the docs... you skeptical infidel! 🤣

I'm not sure how other types of collections like searchkick results would work.

Searchkick is a search paginator, which uses a offset-like pagination under the hood, so no overlapping here.

[JasonBarnabe]

Thanks. Just trying my best to avoid some headache-inducing caching bugs. I was about 95% sure you did it the right way, but the other 5% of me wanted confirmation.

[ddnexus]

Don't worry, I am just kidding! Being skeptical is fundamental. I am skeptical of myself as well... and not only 5%.

That said, :countish does not "cache" anything. It memoizes the count in the pagination links, so I am pretty confident "caching bugs" are not possible.

[JasonBarnabe]

In that case, I don't think it's suited to what I'm trying to accomplish. It would still be great if the documentation elaborated on what it's doing, because it looks like I'm not the first to understand it wrong.

[ddnexus]

I made a little addition to clarify that it memoizes the count "in the links" in the :countish docs. It's small, but it should exclude thinking about "cache".

HTH