Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint --------------------------------------------------------------------------------------------------------------------------
Key: OPENJPA-169 URL: https://issues.apache.org/jira/browse/OPENJPA-169 Project: OpenJPA Issue Type: Improvement Reporter: Patrick Linskey When issuing a JPQL query after changing data that is involved in the access path of the query, OpenJPA must either flush before querying (and therefore obtain a Connection), or load all instances of the potentially-dirty classes into memory and evaluate the query in memory. Now that OpenJPA supports savepoints, we should provide an option to set savepoint, flush, query, and then roll the savepoint back. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.