From: <tr...@do...> - 2014-01-30 17:18:38
|
<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>More recent Virtuoso 6 and 7 releases return CONSTRUCT & DESCRIBE results in a different format via ADO.Net provider</td> </tr> <tr> <td><b>Project:</b></td> <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td> </tr> <tr> <td><b>Created By:</b></td> <td>Rob Vesse</td> </tr> <tr> <td><b>Date:</b></td> <td>2014-01-30 05:17 PM</td> </tr> <tr> <td><b>Comment:</b></td> </tr> <tr> <td colspan="2"><p> I have the simple case of valid SPARQL CONSTRUCT and DESCRIBE queries fixed.</p> <p> </p> <p> However I still need to handle the awkward case of handling the results for non-valid SPARQL queries since we'd usually assume something with more than a single column was SELECT results and we now need to detect the cases where it is not. This requires debugging to see what column names (if any) Virtuoso is using for returning CONSTRUCT and DESCRIBE results in order to detect such a query versus a SELECT (and/or some hacky Contains() check on the raw query string)</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=397" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=397</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> |