I found this issue while investigating a Spring Data Specification API query that is performing poorly. You'll note the Specification API basically wraps the JPA criteria API.

Based on the queries our DBA is showing us, the SQL generated by the JpaSpecificationExecutor is hard-coding numeric values into the SQL. In our case, those numeric values are customer account ids. So the SQL generated for each customer appears different and we never benefit from statement caching.

For us, a property that would allow us to control this behavior would be very helpful.