[mvcalder]

Disclosure, I work at PolyScale.

Prepared statements work fine. Views can be tricky.

The statistical invalidation will in general disable caching on views since their results will change without any corresponding writes (because we only associate writes with the backing tables of the view). Currently our best answer to views is the new stale-while-revalidate flow which revalidates against the db while still serving a hit. With this feature enabled, one can turn off invalidation (if the resulting eventual consistency is acceptable).

More details about how invalidation works here:

https://www.polyscale.ai/blog/approaching-cache-invalidation...