[
https://issues.apache.org/jira/browse/CLEREZZA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Minto van der Sluis updated CLEREZZA-782:
-----------------------------------------
Description:
The class ResultSet only allows indirect access to the variables in the query
results. There are a number of drawbacks to the current solution:
1) the iterator needs to be accessed to get the varNames from
SolutionMapping.getKeySet()
2) I suspect that optional variable present in the Query but not in the
resultset data will not appear in SolutionMapping.getKeySet()
3) If the RestultSet is empty there is no way to determine the variables;
Both Jena and Sesame support retrieving the varNames from their respective
ResultSet.
See also the mailing list conversation at:
http://mail-archives.apache.org/mod_mbox/clerezza-dev/201303.mbox/%3CCALvhUEUzSAoQpNXVmpTcVvR=DxZrFiDJexPgwB=jehc7pjf...@mail.gmail.com%3E
was:
The class ResultSet only allows indirect access to the varNames in the query
results. There are a number of drawbacks to the current solution:
1) the iterator needs to be accessed to get the varNames from
SolutionMapping.getKeySet()
2) I suspect that optional varNames present in the Query but not in the
resultset data will not appear in SolutionMapping.getKeySet()
3) If the RestultSet is empty there is no way to determine the varNames();
Both Jena and Sesame support retrieving the varNames from the ResultSet.
See also the mailing list conversation at:
http://mail-archives.apache.org/mod_mbox/clerezza-dev/201303.mbox/%3CCALvhUEUzSAoQpNXVmpTcVvR=DxZrFiDJexPgwB=jehc7pjf...@mail.gmail.com%3E
> Add meta data (getResultVars) to Sparql ResultSet
> -------------------------------------------------
>
> Key: CLEREZZA-782
> URL: https://issues.apache.org/jira/browse/CLEREZZA-782
> Project: Clerezza
> Issue Type: Bug
> Components: rdf.core
> Reporter: Minto van der Sluis
> Assignee: Minto van der Sluis
>
> The class ResultSet only allows indirect access to the variables in the query
> results. There are a number of drawbacks to the current solution:
> 1) the iterator needs to be accessed to get the varNames from
> SolutionMapping.getKeySet()
> 2) I suspect that optional variable present in the Query but not in the
> resultset data will not appear in SolutionMapping.getKeySet()
> 3) If the RestultSet is empty there is no way to determine the variables;
> Both Jena and Sesame support retrieving the varNames from their respective
> ResultSet.
> See also the mailing list conversation at:
> http://mail-archives.apache.org/mod_mbox/clerezza-dev/201303.mbox/%3CCALvhUEUzSAoQpNXVmpTcVvR=DxZrFiDJexPgwB=jehc7pjf...@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
