Eric,
That needs investigating - it should work. It looks like it might be
connected to Audun's report "Problem persisting N-Triples" as this
erroneous behaviour is characteristic of unflushed caches.
Could you tell me what
fuseki-server --version
reports?
Could you also say what's in the configuration file?
Andy
On 14/01/12 20:32, Eric Scott wrote:
I'm playing with Fuseki using a config file:
fuseki-server --config <config-file> --update dataset
Where <config-file> declares several services, all of which have
associated tdb files.
When I use:
s-update --file <sparql-file> --service
http://localhost:3030/myService/update
The update works just fine, but update does not persist if I kill the
fuseki-server and restart with the same arguments. I note that several
files within the associated TDB directory have updated timestamps, but
querying against the new inserts produces an empty result set.
Are there config options or something else one needs to provide in order
to ensure such persistence?
Thanks,
