If your data arrangements permit, you could hold a record of the contents of the last request on the client side and in the event of a "failure" you could fire a request that reverses that effect. Of course, this only works in some simple cases.
Fuseki doesn't keep a record like that on the server side, and as Andy said, it closes each transaction inside the request-response cycle. Do you need to use Fuseki (HTTP-served SPARQL) in particular, or do you just need SPARQL, or some other technique? With direct access to the dataset, it would be possible to use a transactional dataset implementation like TDB or TIM. --- A. Soroka The University of Virginia Library > On Nov 17, 2016, at 9:41 AM, Nauman Ramzan <[email protected]> wrote: > > It is clear for me. But what about if i wanted to rollback one successful > operation ? Like first I updated one record now I wanted to roll it back > due to any other/outside reason? > > On Thu, Nov 17, 2016 at 3:22 PM, Andy Seaborne <[email protected]> wrote: > >> Each operation is executed in a transaction but there is no HTTP >> operations to start and end a transaction of several HTTP requests. >> >> You can combine multiple SPARQL Update operations into one HTTP request >> using ";" between SPARQL Update operations in the HTTP body. >> >> Andy >> >> >> >> On 17/11/16 10:52, Nauman Ramzan wrote: >> >>> I wanted to ask is there Transaction query in SPARQL like begin, commit, >>> rollback . >>> Thank you >>> >>>
