Closed niniemann closed 5 years ago
Currently I dont see another breaking change for the SPARQLQuery. But I have a few ideas to extend it to make it more comfortable. I will check this in the next days.
I dont see any other braking changes on the SPARQLQuery in the next releases. So this is fine for me.
I noticed that it can be a bit difficult to work with the results from a SPARQLQuery, since currently only the string-representation is passed. On the way there, resources lose their
<>
brackets, and could be mistaken for literals.Hence, this PR extends the return type of SPARQLQuery: It is still a vector of maps, but the value-part of the map has changed from
std::string
tostd::pair<ValueType, std::string>
, whereValueType
specifies whether the bound value is a resource, literal or blank node.This will break stuff, but I still think it is a necessary update. Did I forget anything that should be included here, to avoid yet another breaking change?