[
https://issues.apache.org/jira/browse/OPENJPA-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128579#comment-18128579
]
ASF subversion and git services commented on OPENJPA-2951:
----------------------------------------------------------
Commit f8a87d426c8c066229c98fa2b500c5d45bc7e834 in openjpa's branch
refs/heads/OPENJPA-2951 from Maxim Solodovnik
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=f8a87d426 ]
Merge branch 'master' into OPENJPA-2951
> 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
> Priority: Major
> 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)
