From: <tr...@do...> - 2012-10-03 19:24:15
|
<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>Refactor how GROUP BY, Aggregates and Project Expressions are applied</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>0.8.0 RC 1</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>Refactor</td> </tr> <tr> <td><b>Description:</b></td> </tr> <tr> <td colspan="2"><p> The current method of applying GROUP BY, Aggregates and Project Expressions works and passes the official tests but implementation wise is somewhat different from other implementations like ARQ. The code in question is quite convuluted and hard to read making it difficult to maintain or extend going forward.</p> <p> This task is to refactor the code appropriately, this includes the following:</p> <ul> <li> Move code for group calculation and GroupMultiset population fully into GroupBy</li> <li> Move code for aggregate calculation into GroupBy</li> <li> Properly handle the case of aggregates with no GROUP BY - create a GroupMultiset containing a single group</li> <li> Handle project expressions as Extend over the inner algebra</li> <li> Remove separate Project operator since it's actual intended function is already handled by Select</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=284" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=284</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> |