Re: Delete/Insert single graph in dataset

To load, yes. Just use the --graph=IRI (Act on a named graph) switch. You'll find all the useful switches by executing tdbloader --help. Neither of the loaders will delete anything, ever. I believe that tdbquery can execute SPARQL Update, which you could use for the purpose. If your database is

Delete/Insert single graph in dataset

Can I use tdbloader to load or delete a single graph from a dataset? Or maybe some other command line tool?

Re: Query performance over 1 dataset, many graphs

To some extent it will depend on the dataset implementation in use, but the two most likely are TDB and TIM (transactional in-memory) and for either of those, there is no particular hit. Both use covering indexes that include orderings to prevent that. If you are using some other (not core

Query performance over 1 dataset, many graphs

If I query my dataset as "SELECT * FROM ...", is there a performance hit if is in the same dataset with many (10s or 100s, more?) other graphs? Or is this fact completely irrelevant?

Re: RDF API or Jena rule

Thank you, And what is SPIN then? Is it the combination of Jena and SPARQL? If it is, then it would be better than Jena, for sure? But it is still Jena which are using in most of semantic web applications. On Sun, Apr 16, 2017 at 3:06 PM, Lorenz B. < buehm...@informatik.uni-leipzig.de> wrote: >

Re: RDF API or Jena rule

I think you are confused. Rules are for inference, RDF API is for manipulating RDF from Java. They are orthogonal. On Sun, Apr 16, 2017 at 1:01 PM, javed khan wrote: > Is there any advantage of Jena rule (speed etc) over RDF API? For example, > a functionality in our

RDF API or Jena rule

Is there any advantage of Jena rule (speed etc) over RDF API? For example, a functionality in our application we achieve using rule and RDF, which way will be best to follow? I am asking this because in my application I have used few rules but I could easily got the same result using RDF API.