Databases
StackOverflow2013
Postsdbo
PODifferent number of results with sesame2 and jena
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODifferent number of results with sesame2 and jena
    primarykey
    data
    text
    <p>I'm writing some queries which are being run on both jena and sesame2. Most of them are working correctly under sesame2 except when i specify the depth of a path. For example, if I run this query under sesame it gives me 8 results whereas jena gives 217 (the correct number).</p> <pre><code>PREFIX edge: &lt;http://danielfrentz.com/edge#&gt; PREFIX property: &lt;http://danielfrentz.com/property#&gt; select distinct ?start ?reached where{ ?start property:id \"v1\". ?start (edge:uses | edge:implements | edge:extends)+ ?reached. filter(?start != ?reached)} </code></pre> <p>So my question is, does sesame2 have a different definition of the path depth syntax? or is there another reason why I might be getting different results?</p> <p>Thanks. </p> <p>Additional details:</p> <p>I'm using 2.6.10 and trying out 2.7 beta.</p> <p>The smallest example graph I have is the following (sorry its so long):</p> <pre><code>@prefix edge: &lt;http://danielfrentz.com/edge#&gt;. @prefix edge: &lt;http://danielfrentz.com/property#&gt;. &lt;http://danielfrentz.com/v2&gt; &lt;http://danielfrentz.com/property#name&gt; "Class3". &lt;http://danielfrentz.com/v2&gt; &lt;http://danielfrentz.com/property#abstract&gt; "false". &lt;http://danielfrentz.com/v2&gt; &lt;http://danielfrentz.com/property#type&gt; "class". &lt;http://danielfrentz.com/v2&gt; &lt;http://danielfrentz.com/property#namespace&gt; "com.example". &lt;http://danielfrentz.com/v2&gt; &lt;http://danielfrentz.com/property#id&gt; "v2". &lt;http://danielfrentz.com/v1&gt; &lt;http://danielfrentz.com/property#name&gt; "Class2". &lt;http://danielfrentz.com/v1&gt; &lt;http://danielfrentz.com/property#abstract&gt; "false". &lt;http://danielfrentz.com/v1&gt; &lt;http://danielfrentz.com/property#type&gt; "class". &lt;http://danielfrentz.com/v1&gt; &lt;http://danielfrentz.com/property#namespace&gt; "com.example". &lt;http://danielfrentz.com/v1&gt; &lt;http://danielfrentz.com/property#id&gt; "v1". &lt;http://danielfrentz.com/v3&gt; &lt;http://danielfrentz.com/property#name&gt; "Class4". &lt;http://danielfrentz.com/v3&gt; &lt;http://danielfrentz.com/property#abstract&gt; "false". &lt;http://danielfrentz.com/v3&gt; &lt;http://danielfrentz.com/property#type&gt; "class". &lt;http://danielfrentz.com/v3&gt; &lt;http://danielfrentz.com/property#namespace&gt; "com.example". &lt;http://danielfrentz.com/v3&gt; &lt;http://danielfrentz.com/property#id&gt; "v3". &lt;http://danielfrentz.com/v4&gt; &lt;http://danielfrentz.com/property#name&gt; "AbstractClass1". &lt;http://danielfrentz.com/v4&gt; &lt;http://danielfrentz.com/property#abstract&gt; "true". &lt;http://danielfrentz.com/v4&gt; &lt;http://danielfrentz.com/property#type&gt; "class". &lt;http://danielfrentz.com/v4&gt; &lt;http://danielfrentz.com/property#namespace&gt; "com.example". &lt;http://danielfrentz.com/v4&gt; &lt;http://danielfrentz.com/property#id&gt; "v4". &lt;http://danielfrentz.com/v0&gt; &lt;http://danielfrentz.com/property#name&gt; "Class1". &lt;http://danielfrentz.com/v0&gt; &lt;http://danielfrentz.com/property#abstract&gt; "false". &lt;http://danielfrentz.com/v0&gt; &lt;http://danielfrentz.com/property#type&gt; "class". &lt;http://danielfrentz.com/v0&gt; &lt;http://danielfrentz.com/property#namespace&gt; "com.example". &lt;http://danielfrentz.com/v0&gt; &lt;http://danielfrentz.com/property#id&gt; "v0". &lt;http://danielfrentz.com/v5&gt; &lt;http://danielfrentz.com/property#name&gt; "Interface1". &lt;http://danielfrentz.com/v5&gt; &lt;http://danielfrentz.com/property#abstract&gt; "true". &lt;http://danielfrentz.com/v5&gt; &lt;http://danielfrentz.com/property#type&gt; "interface". &lt;http://danielfrentz.com/v5&gt; &lt;http://danielfrentz.com/property#namespace&gt; "com.example". &lt;http://danielfrentz.com/v5&gt; &lt;http://danielfrentz.com/property#id&gt; "v5". &lt;http://danielfrentz.com/v3&gt; &lt;http://danielfrentz.com/edge#extends&gt; &lt;http://danielfrentz.com/v4&gt;. &lt;http://danielfrentz.com/v2&gt; &lt;http://danielfrentz.com/edge#uses&gt; &lt;http://danielfrentz.com/v3&gt;. &lt;http://danielfrentz.com/v4&gt; &lt;http://danielfrentz.com/edge#uses&gt; &lt;http://danielfrentz.com/v2&gt;. &lt;http://danielfrentz.com/v5&gt; &lt;http://danielfrentz.com/edge#uses&gt; &lt;http://danielfrentz.com/v0&gt;. &lt;http://danielfrentz.com/v1&gt; &lt;http://danielfrentz.com/edge#implements&gt; &lt;http://danielfrentz.com/v5&gt;. &lt;http://danielfrentz.com/v0&gt; &lt;http://danielfrentz.com/edge#uses&gt; &lt;http://danielfrentz.com/v1&gt;. </code></pre> <p>The query is:</p> <pre><code>PREFIX edge: &lt;http://danielfrentz.com/edge#&gt; PREFIX property: &lt;http://danielfrentz.com/property#&gt; select distinct ?start ?reached where{ ?start property:id \"v1\". ?start (edge:uses | edge:implements | edge:extends){1,3} ?reached. FILTER (?start != ?reached)} </code></pre> <p>and the results are:</p> <pre><code>start start=http://danielfrentz.com/v1 reached reached=http://danielfrentz.com/v5 </code></pre> <p>there should be 2 results not 1. </p> <p>I should also add that when I dont use a property path (ie i use + instead of {1,3}) it gives the correct number of results.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser1690293
    1. USuser1690293
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODifferent number of results with sesame2 and jena
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODifferent number of results with sesame2 and jena
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODifferent number of results with sesame2 and jena
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe Sesame people would probably appreciate a complete, minimal example. Complete=>some data and the expected result ; minimal=>no larger than necessary (not 217 results, as simple a query as possible).
      singulars
      1. PODifferent number of results with sesame2 and jena
      1. USAndyS
    2. COIn addition, please let us know which version of Sesame you are using. Property paths are a new feature. Both the official definition in the SPARQL spec and the implementation in Sesame have changed several times over various releases.
      singulars
      1. PODifferent number of results with sesame2 and jena
      1. USJeen Broekstra
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload