From: <tr...@do...> - 2013-11-25 22:02:10
|
<p>The following issue has been added to a project that you are monitoring.</p> <table border="0"> <tr> <td width="90px" valign="top"><b>Title:</b></td> <td>Unexpected SPARQL results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</td> </tr> <tr> <td><b>Project:</b></td> <td>Core Library (dotNetRDF.dll)</td> </tr> <tr> <td><b>Created By:</b></td> <td>Alexandre Bouffard</td> </tr> <tr> <td><b>Milestone:</b></td> <td>Unassigned</td> </tr> <tr> <td><b>Category:</b></td> <td>Query</td> </tr> <tr> <td><b>Priority:</b></td> <td>High</td> </tr> <tr> <td><b>Type:</b></td> <td>Bug</td> </tr> <tr> <td><b>Description:</b></td> </tr> <tr> <td colspan="2"><p> Hi,</p> <p> I think I found a bug related to the SPARQL query engine but I am not 100% sure.</p> <p> I am computing the delta between two graphs in memory (TripleStore class) using a SPARQL query.</p> <ul> <li> When using the MINUS operator, it works as expected.</li> <li> When using the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" pattern, I get unexpected results under some circumstances I have not pinpointed yet</li> </ul> <p> Please see the attached unit test. Note that:</p> <ul> <li> Expected results are obtained when removing one of the two triples from the Turtle data string.</li> <li> Expected results are obtained when asserting triples instead of parsing them (as far as I tried).</li> </ul></td> </tr> </table> <p> More information on this issue can be found at <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</a></p> <p style="text-align:center;font-size:8pt;padding:5px;"> If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options. </p> |