From: <tr...@do...> - 2014-01-15 14:36:12
|
<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>Bug in complex property path evaluation</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>Milestone:</b></td> <td>1.0.4</td> </tr> <tr> <td><b>Category:</b></td> <td>Query</td> </tr> <tr> <td><b>Priority:</b></td> <td>Normal</td> </tr> <tr> <td><b>Type:</b></td> <td>Bug</td> </tr> <tr> <td><b>Description:</b></td> </tr> <tr> <td colspan="2"><p> A user on StackOverflow has discovered a bug in the evaluation of complex property paths - <a href="http://stackoverflow.com/questions/21128667/dotnetrdf-exception-the-value-of-a-variable-in-a-set-cannot-be-changed-by-inte#21128667">http://stackoverflow.com/questions/21128667/dotnetrdf-exception-the-value-of-a-variable-in-a-set-cannot-be-changed-by-inte#21128667</a></p> <p> At a glance I suspect it is caused by the nesting of the arbitrary length property paths.</p> <p> Likely won't have time to debug/fix until 1.0.4</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=395" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=395</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> |