Mario - thanks for the details.
graph.QueryHandler is not related to SPARQL execution (and it changed in
May in an incompatible way so we have a fairly good idea no one external
is using it).
Andy
On 06/09/12 10:37, Mario Ds Briggs wrote:
We do implement a number of the interfaces since we support using DB2 via
the JENA API,
the standard XXXFactory and related ones for query execution and then
resultset handling
the Dataset related ones - Dataset, DatasetGraph, Transactional,
GraphStore
Presumably, you don't do anything in special support of reification as
it's handled
<<
Yes.
Mario
From: Andy Seaborne <[email protected]>
To: [email protected]
Date: 09/05/2012 07:22 PM
Subject: Re: Evolution: BulkUpdateHandler / Reification / QueryHandler
Sent by: Andy Seaborne <[email protected]>
On 05/09/12 12:37, Mario Ds Briggs wrote:
Andy,
In DB2 we extend GraphBase and then override some of the methods... so
just
clarifying
That's useful to know. Do you hook into Jena in other ways as well?
My proposal is that the useful operations are moved to Graph, the code
for the withReifications forms migrate to the only callers in ModelCom.
<<
Today when Model.add(Model) is called by end user, the code flows to
ModelCom.add(Model)
ModelCom.add(Model,boolean)
BulkUpdateHandler().add(Graph, boolean)
So you are saying that ModelCom will now call Graph.add(Graph) and so as
long as one overrides the new Graph.add(Graph) method, ModelCom would
invoke it.
Yes - the functionality of Model.add(Model) remains the same but the
Graph operation migrates.
Presumably, you don't do anything in special support of reification as
it's handled (if there is anything to do - there isn't in the default
'Standard' mode) in GraphBase.
Andy
thanks
Mario
