Join GitHub today
usage of any() pollutes query cache #1231
We are using Spring Data together with query dsl 3.5.1.
We have several queries that make use of the any() expression.
Unfortunately each time querydsl generates the JPA query this name is different.
Would it be possible to implement a naming strategy that produces reproducible names for the any()-tables?
I don't quite know how Spring Data resolves query objects, but we lazily initialize the any paths inside the collection paths, to reuse those instances.
However, I think it should be okay to think of a naming strategy, but we transform any usage to a join via parent. since this should be a temporary alias, it must not collide with other names.