That is not exactly how I read "eclipselink.jdbc.bind-parameters". Unless I misread, that seems to control whether they create PreparedStatements (and use JDBC parameter binding) or create each SQL statement for each request and use Statement. So not really the same situations.

Personally I am ok with a new setting that controls how literals ultimately get rendered. I am not sure how simple that is with the old JPA Criteria translator. I'd instead opt to include that with the SQM work in 6.0. I could even see a solution based on a pluggable SPI contract.