RDFLib/rdflib — Issue #148: Reworking of Query result handling
Author: gjhiggins
Created: 2012-02-20 08:33:50+00:00
State: open

gromgull, 2011-02-18T21:49:01.000Z

Purpose of code changes on this branch:

(note there is no branch, only attached patch)

This introduces a richer Result object for queries, it is meant to be backwards compatible to the SPARQLResults we already get from the sparql impl in rdfextras.

It also introduces plugin points for ResultParsers and ResultSerializers
A matching patch for rdfextras with parser/serializer support for xml and json sparql results is coming shortly.

When reviewing my code changes, please focus on:
Does this break anything? :)

After the review, I'll merge this branch into:
trunk
/trunk

Comment 1 by gromgull
patch

Comment 2 by gromgull
I forgot to mention - this obviously restricts us to the four types of queries defined in the new class, select, ask, describe, construct. I cannot think of any, but perhaps someone else has a use-case where this is problematic?

Comment 3 by gromgull
Clearly it was too late at night for me to remember most of the things I wanted to say about this:

This would also also deprecate the QueryResult plugin stuff we have now. I have problem finding a scenario where you would want to provide a query processor, but NOT a result plugin? Or any where you would want to mix and match? For the sparql implementation in rdfextras, the two are very tightly coupled.

A future patch, (not yet written), will make the rdfextras sparql processor work with this.

Comment 4 by gromgull
new more correct patch :)

See also http://code.google.com/p/rdfextras/source/list?r=query-result-cleanup

Comment 5 by gromgull
Moved the patch to a hg branch, query-result-cleanup:

http://code.google.com/p/rdflib/source/browse/?r=query-result-cleanup

Comment 6 by gromgull
Ok - I'll give you until next week, when I am back from holiday I will merge if noone says anything :)

Comment 7 by gromgull
This issue was closed by revision d45003524720.