A question about using Fuseki and TBD transactions from a Java application:

Are the transaction boundaries implicit per SPARQL operation?

If multiple operations are included in one request, by definition
either they all succeed or they all fail.

Is there some way through the Java TDB API to connect to Fuseki and
execute multiple sequential requests to query and update the
underlying Fuseki TDB model as part of one ACID transaction. i.e. the
reads before and between the updates are all consistent?

I thought I read something to that effect, but cannot find it, and am
questioning my recollection.

Thanks
-Patrick

Reply via email to