OpenJPA
  1. OpenJPA
  2. OPENJPA-169

Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Patrick Linskey
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development