From: <tr...@do...> - 2013-03-20 02:59:40
|
<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>GROUP_CONCAT fails on non-literal inputs</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.0</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> This <a href="http://answers.semanticweb.com/questions/21699/sparql-select-using-group_concat-column-retrieve-a-string-of-commas-only?page=1&focusedAnswerId=21701#21701">question</a> highlights a bug in our implementation of GROUP_CONCAT in that it will only concatenate literals when it should be capable of concatenating a mixture of URIs and literals</p> <p> E.g</p> <p> The following returns nothing:</p> <p> SELECT (GROUP_CONCAT(?s) AS ?subjects) WHERE { ?s ?p ?o }</p> <p> Yet forcing things to be literals yields a result:</p> <p> SELECT (GROUP_CONCAT(STR(?s)) AS ?subjects) WHERE { ?s ?p ?o }</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=340" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=340</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> |