> does it also affect the query execution or the result set? I think it should bomb. Let me know what you see -- in terms of eventual SQL query that gets executed on the database. You can switch on logging to print SQL queries as well as their parameters.
Because of many practical complexities involved in parameter rebinding (further complicated because we insert internal parameters as well with the user-supplied ones), we detect few cases where we can not rebind and automatically skip caching/reusing the target query. The user application can also avail the facility to bypass this query caching behavior at multiple level (for a specific query, for a subset of queries, for a transaction, for a session etc.) [1] without completely sacrificing the performance benefit of this reuse facility carte blanche. [1] http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_cache_querysql ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/Strange-warnings-about-query-parameters-tp5431171p5432684.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
