History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-839
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Jeen Broekstra
Reporter: Jeen Broekstra
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sesame

property path with more than two path alternatives does not get parsed correctly

Created: 19/Sep/11 10:37 PM   Updated: 19/Sep/11 10:55 PM
Component/s: SPARQL
Affects Version/s: 2.5.0
Fix Version/s: 2.5.1


 Description   
Reported by Pointbreak on the mailinglist:

The query "SELECT ?result {<u:start> <u:1>|<u:2>|<u:3> ?result}" results
in the following TupleExpr when parsed by Sesame 2.5.0:

Projection
   ProjectionElemList
      ProjectionElem "result"
   Union
      StatementPattern
         Var (name=-const-1, value=u:start, anonymous)
         Var (name=-const-2, value=u:1, anonymous)
         Var (name=result)
      StatementPattern
         Var (name=-const-3, value=u:start, anonymous)
         Var (name=-const-4, value=u:2, anonymous)
         Var (name=result)

This seems incorrect. There should be a second union with the <u:3>
predicate.



 All   Comments   Change History      Sort Order:
Comment by Jeen Broekstra [19/Sep/11 10:55 PM]
Fix checked in. Query now results in the following parse tree:

Projection
   ProjectionElemList
      ProjectionElem "result"
   Union
      StatementPattern
         Var (name=-const-1, value=u:start, anonymous)
         Var (name=-const-2, value=u:1, anonymous)
         Var (name=result)
      Union
         StatementPattern
            Var (name=-const-3, value=u:start, anonymous)
            Var (name=-const-4, value=u:2, anonymous)
            Var (name=result)
         StatementPattern
            Var (name=-const-5, value=u:start, anonymous)
            Var (name=-const-6, value=u:3, anonymous)
            Var (name=result)