Cool to see the caching feature being released! We use honeysql extensively, but most of the queries use https://www.postgresql.org/docs/8.3/queries-values.html; resulting in a dynamic amount of parameters most queries (even though most of the query is the same). Would we be able to leverage the new caching mechanic?

@jeroen.dejong I'd have to see how you're generating those in HoneySQL to offer an opinion, but I suspect if the number of parameters is varying, the best you'll get is cached generation for each multiple of parameters (since it's the data structure that is used as a cache key and I think that's going to vary based on the number of parameters, right?).