On 08/11/11 23:11, Robert Vesse wrote:
Hi Andy
So my approach certainly works as far as constructing a dataset goes
but it still doesn't do what I wanted it to do. The problem is that
it goes away and builds a fresh dataset from scratch based on the
URIs that get passed to it. So when I tested it against TDB I find
that whenever I specify a FROM/FROM NAMED I get the wrong results
because it builds the dataset by loading the
"loading the" ??? URL from the web?
Fuseki does this when the request is to the general query processor (on
"/sparql" and code in SPARQL_QueryGeneral).
I commented out the code in SPARQL_QueryDataset.validateQuery which
checked for FROM/FROM NAMED. Then I made a query to a TDB dataset is
getting to TDB and triggering dynamic dataset processing.
(current development codebase)
Yes, QueryEngineTDB creates a new DatasetGraph internally but it's
rooted to the database but I'm guessing this is what you mean.
What I want it to do is to pull out the graphs to be used from the
underlying storage but I have no idea whether that is in any way
possible? Perhaps you can enlighten me on this because I can't see
any obvious way of doing this in code.
If this is not possible then we're stuck with just disabling the
error thrown when FROM/FROM NAMED is specified and hoping that the
underlying store supports this feature somehow but certainly TDB
appears to ignore it entirely.
TDB does not ignore it - see QueryEngineTDB and
DynamicDatasets.dynamicDataset.
Andy
