[
https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307263#comment-16307263
]
A. Soroka commented on JENA-1457:
---------------------------------
Just to be extra-clear: TIM doesn't require explicit transactions, but any
non-transactional calls on it get auto-wrapped per call into
single-call-payload transactions. Expensive and slow! So one can mix explicit
and non-explicit transactional behavior against TIM (there really is no
non-transactional behavior for TIM), but users are well-advised to be as
explicit as possible.
So it seems like TIM or TDB2 graphs are always transactional and other dataset
impls, not so much, but I don't know that we can represent very well that at
this point in the API/contracts. It seems like that boat has sailed on the same
tide that sent immutable graphs out to sea. Maybe we can think about
representing transactionality differently in a new API?
> Graph contract tests do not properly support transactions
> ---------------------------------------------------------
>
> Key: JENA-1457
> URL: https://issues.apache.org/jira/browse/JENA-1457
> Project: Apache Jena
> Issue Type: Bug
> Components: Core
> Reporter: Claude Warren
> Priority: Minor
>
> The Contract test for Graphs do not properly support transactions.
> Specifically, if the graph supports transactions all actions should be
> enclosed within a transaction.
> The easiest test for this is to test the GraphTxnTDB implementation as it
> will fail if transactions are not properly used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
