[
https://issues.apache.org/jira/browse/JENA-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123038#comment-13123038
]
Andy Seaborne commented on JENA-97:
-----------------------------------
The right answers seem to be:
-------------------------------------------------------------
| aUri | name |
=============================================================
| <https://front.side/jazz/people/eomer.nt> | "eomer" |
| <https://front.side/jazz/people/eomer.nt> | "eowyn" |
| <https://front.side/jazz/people/eomer.nt> | "theodred" |
| <https://front.side/jazz/people/eowyn.nt> | "eowyn" |
| <https://front.side/jazz/people/eowyn.nt> | "theodred" |
| <https://front.side/jazz/people/theodred.nt> | "theodred" |
-------------------------------------------------------------
which I obtained by manually creating the 9 triple graph of relevant
information.
GRAPH ?g stop the pattern matching over different graphs.
I think that two things go wrong:
In old versions, rewriting to quads didn't work on paths. The fix (a change in
ARQ) does not seem to correctly interact with TDB.
Explicit naming works:
SELECT *
FROM <urn:x-arq:UnionGraph>
WHERE
{ ?aUri rdf:type people:Person .
?aUri (foaf:knows)*/foaf:name ?name
}
or
SELECT * # ?aUri ?name
WHERE {
GRAPH <urn:x-arq:UnionGraph> {
?aUri a people:Person .
?aUri foaf:knows*/foaf:name ?name
}
}
Exact details of property paths involving * have changed (some time ago but
this year) in line with SPARQL WG decisions.
> 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
