[
https://issues.apache.org/jira/browse/CLEREZZA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873989#action_12873989
]
Reto Bachmann-Gmür commented on CLEREZZA-219:
---------------------------------------------
classic ACID-Transaction have been repeatedly wished. on the other hand,
systems that do support transactions generally recommend not using them because
of the performance implications.
The described use case doesn't seem very convincing as the check could easily
be done before adding any triples. As a general pattern it might be good to do
the addtions to a SimpleMGraph and only if this worked at this MGraph a whole
to the content-graph.
> in rdf.core: Introduce atomicity and isolation for graph manipulation
> ---------------------------------------------------------------------
>
> Key: CLEREZZA-219
> URL: https://issues.apache.org/jira/browse/CLEREZZA-219
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Manuel Innerhofer
>
> It should be possible to modify a graph and commit all changes to the graph
> at the same time or dismiss the modifications.
> Use Case:
> A POST request with form data is sent to the clerezza platform. The form-data
> of the request contains the contact information of a user. The clerezza
> platform starts to fill the data into the content graph. At one point the
> submitted email address is check for validity and throws an
> IlleagalFormatException. It is desirable that the information already added
> to the graph is not commited and can be dismissed by the server code.
> Furthermore the already added data should have never been visible to other
> processes accessing the content graph. Only when a explicit "commit" command
> was executed should the modifications be visible to other processes only
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
