[
https://issues.apache.org/jira/browse/JENA-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375349#comment-15375349
]
A. Soroka commented on JENA-1209:
---------------------------------
Right, I meant more that the other option would be: you can get exclusive mode
immediately, and then when any transactions that were open at the time
eventually try to commit, the underlying store will throw an exception and
force them to abort instead. Actually, I wanted to recommend against that, so
it's all good. Definitely the right approach was taken, I think, for whatever
that's worth! {grin}
> Add "exclusive mode" for TDB
> ----------------------------
>
> Key: JENA-1209
> URL: https://issues.apache.org/jira/browse/JENA-1209
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> In exclusive mode, the current thread is guaranteed there are no other read
> or write transactions active.
> This allows specialized code to _*very*_ carefully manipulate the internals
> of the database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
