From: <tr...@do...> - 2014-02-01 21:38:59
|
<p>A new comment has been added to the following issue.</p> <table border="0"> <tr> <td width="90px" valign="top"><b>Title:</b></td> <td>Unexpected SPARQL query result for MINUS inside UNION and specifying named graph</td> </tr> <tr> <td><b>Project:</b></td> <td>Core Library (dotNetRDF.dll)</td> </tr> <tr> <td><b>Created By:</b></td> <td>Rob Vesse</td> </tr> <tr> <td><b>Date:</b></td> <td>2014-02-01 09:38 PM</td> </tr> <tr> <td><b>Comment:</b></td> </tr> <tr> <td colspan="2"><p> So it turns out getting to the airport early gives you more free time than you thought. This bug actually has nothing to do with MINUS its just the structure of the query happens to show a low level bug up and give the impression that MINUS is working incorrectly.</p> <p> </p> <p> The actual bug is in the compilation of queries into SPARQL algebra and for some types of leaf node it is incorrectly compiling modifiers on that node. So in the test case given here the left hand side of the UNION looks at the default graph which is empty instead of the named graph as the query asks.</p> <p> </p> <p> I have made the fix on a branch for the specific case highlighted here but I think there are a couple more cases where the issue might occur and need to review further to determine what those are and also verify interaction of the fix with other query elements before I merge this into trunk.</p></td> </tr> </table> <p> More information on this issue can be found at <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=398" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=398</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> |