Does Fuseki Support Manual Creation of Transactions?

[Brandon Sara <Br...@pointclickcare.com.INVALID>]

Does Fuseki support the creation of transactions that can span multiple requests?

If so, would the following sequence of events be true or no?
1. I start a transaction
2. I submit a query to get some data for and update I want to perform
3. An update is submitted by a separate client
4. The update from the separate client is put on hold
5. I submit an update
6. I submit another query to verify changes
7. I commit & end the transaction
8. The update submitted in step 3 is allowed to proceed
No PHI in Email: PointClickCare and Collective Medical, A PointClickCare Company, policies prohibit sending protected health information (PHI) by email, which may violate regulatory requirements. If sending PHI is necessary, please contact the sender for secure delivery instructions.

Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

Re: Does Fuseki Support Manual Creation of Transactions?

[Andrii Berezovskyi <an...@kth.se>]

Hello Brandon,

Last time I checked, this was not possible in Jena or standard SPARQL (Update) 1.1. RDF4J has such an extension: https://rdf4j.org/documentation/reference/rest-api/#tag/Transactions

In SPARQL 1.1, the suggested approach is to combine multiple SPARQL (only update) queries into one request and have them execute in a single transaction context, e.g. https://www.w3.org/TR/2013/REC-sparql11-update-20130321/#example_10

–Andrew.

On 30 Jun 2023, at 23:24, Brandon Sara <Br...@pointclickcare.com.INVALID> wrote:

Does Fuseki support the creation of transactions that can span multiple requests?

If so, would the following sequence of events be true or no?
1. I start a transaction
2. I submit a query to get some data for and update I want to perform
3. An update is submitted by a separate client
4. The update from the separate client is put on hold
5. I submit an update
6. I submit another query to verify changes
7. I commit & end the transaction
8. The update submitted in step 3 is allowed to proceed
No PHI in Email: PointClickCare and Collective Medical, A PointClickCare Company, policies prohibit sending protected health information (PHI) by email, which may violate regulatory requirements. If sending PHI is necessary, please contact the sender for secure delivery instructions.

Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.