metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kasper Sørensen (JIRA) <j...@apache.org>
Subject [jira] [Commented] (METAMODEL-238) Error when using GROUPBY and ORBERBY with different fields
Date Thu, 10 Mar 2016 15:28:40 GMT

    [ https://issues.apache.org/jira/browse/METAMODEL-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189428#comment-15189428
] 

Kasper Sørensen commented on METAMODEL-238:
-------------------------------------------

To my knowledge then you also HAVE TO group on the country in order to ORDER BY on it. And
then you can choose to wrap _that_ in a subquery to again aggregate the total_children and
disregard (not select) country.

> Error when using GROUPBY and ORBERBY with different fields
> ----------------------------------------------------------
>
>                 Key: METAMODEL-238
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-238
>             Project: Apache MetaModel
>          Issue Type: Bug
>    Affects Versions: 4.5.1
>            Reporter: Alessandro Portosa
>
> MetaModel does not act as expected when providing it a different field for GROUPING and
ORDERING.
> Let's say the we have a table with the following columns: total_children, city, country.
> 1) If i use 
> {code}SELECT SUM(total_children) AS total_children_SUM, city AS city FROM schema.table
GROUP BY city{code}
> I get the right results.
> 2) If i use 
> {code}SELECT SUM(total_children) AS total_children_SUM , city AS city FROM schema.table
GROUP BY city ORDER BY city asc{code}
> then I get the right results.
> 3) But if I use 
> {code}SELECT SUM(total_children) AS total_children_SUM, city AS city FROM schema.table
GROUP BY city ORDER BY country asc{code}
> I get the wrong results.
> I do always get results, but these are the same as 1) where no ordering was
> required. The same happen with I use any other field that is not city
> (which is the field that I'm using for the grouping).
> This is how I use it:
> {code}
>    Query query = dataContext.parseQuery(sqlQuery);
>    CompiledQuery cQuery = dataContext.compileQuery(query);
>    DataSet dataSet = dataContext.executeQuery(cQuery);
> {code}
> The used DataContext is a PojoDataContext.
> No error or exception. Just wrong data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message