[jira] [Issue Comment Deleted] (OPENJPA-169) Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint

["Rick Curtis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Curtis updated OPENJPA-169:
--------------------------------
    Comment: was deleted

(was: http://www.acalculator.com/estate-tax-planning.html
http://www.acalculator.com/72t-calculator.html
http://www.acalculator.com/72t-calculator.html
http://www.acalculator.com/savings-calculators.html
http://www.acalculator.com/debt-calculators.html
http://www.acalculator.com/breakeven-analysis-calculator.html
http://www.acalculator.com/electricity-charge-payment-calculator.html)

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)