[
https://issues.apache.org/jira/browse/JENA-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123090#comment-13123090
]
Simon Helsen commented on JENA-97:
----------------------------------
ok, so I debugged this as well and I see that the way tdbquery works, it avoids
the mulitiple selection, but if you set a breakpoint at line 181 in
com.hp.hpl.jena.sparql.resultset.TextOutput and look at
QuerySolution rBind =...
you'll notice that aUri is in the binding more than once. While I can easily
work around this, I want to point out that in TDB 0.8.7, this binding did not
occur twice. My worry is that this double occurrence of aUri in the
QuerySolution is the symptom of an underlying problem which I don't understand
if you can confirm this is not the case (and I should not assume that bindings
of a ResultSet are unique), then I will simply fix my own code and we can close
this defect
> TDB 0.9.0 snapshot sometimes returns a SELECT binding twice
> -----------------------------------------------------------
>
> Key: JENA-97
> URL: https://issues.apache.org/jira/browse/JENA-97
> Project: Jena
> Issue Type: Bug
> Components: TDB
> Environment: tx-tdb-0.9.0-20111006.082548-13-dist
> Reporter: Simon Helsen
> Assignee: Andy Seaborne
> Attachments: quads.txt
>
>
> Very sometimes (rare), it seems that a result set will repeat the first
> SELECT binding. E.g.
> SELECT ?a ?b ...
> will bind ?a twice in the result set. It only happens quite rarely, but the
> same queries behave correctly in TDB 0.8.7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
