I would prefer to use the model api. There is reification, deletion, inserting, etc.... I will take a look at the DatasetAccessor. I am only applying changes to a named graph.
On Wed, Jan 28, 2015 at 2:44 PM, Rob Vesse <[email protected]> wrote: > Via Fuseki > > Attempting to do anything that bypasses Fuseki and accesses the TDB data > directory directly is ill-advised, shouldn't work (there is process level > locking on TDB data directories) and is highly likely to corrupt your data. > > One option would be to use SPARQL updates to supply your changes. > > However if your changes involve complex graph manipulations best done with > the Model API AND they only apply to a specific named graph then you could > use the graph store protocol to replace an existing named model - see > DatasetAccessor which is the Jena API to the protocol and its methods such > as getModel() and putModel() > > Rob > > On 28/01/2015 10:58, "Trevor Donaldson" <[email protected]> wrote: > > >Hi all, > > > >What would be the best way to update a TDB store behind Fuseki. I have a > >standalone app that needs to update (delete and insert) statements as well > >as insert new statements. I was thinking that I could use the Jena api > >with > >an in memory model and then somehow send the deletes first to fuseki, then > >send the inserts to fuseki. Not exactly sure how to accomplish this. Is > >this possible? > > > >Thanks, > >Trevor > > > > >
