Maxim Solodovnik created OPENJPA-2951:
-----------------------------------------
Summary: Full context flush after in-memory bulk update/delete
Key: OPENJPA-2951
URL: https://issues.apache.org/jira/browse/OPENJPA-2951
Project: OpenJPA
Issue Type: Sub-task
Components: jpa
Affects Versions: 4.2.0
Reporter: Maxim Solodovnik
Fix For: 4.2.0
Discussion thread:
https://github.com/apache/openjpa/pull/144#discussion_r3682999520
**(medium)** The new `_broker.flush()` after in-memory bulk delete (and update
at line 1156) flushes the entire persistence context as a side effect of
`executeUpdate()`, changing when unrelated pending changes hit the database
(locks, triggers, constraint timing). Is flushing only the affected instances
feasible, or is the full flush deliberate?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
