[prev in list] [next in list] [prev in thread] [next in thread] 

List:       turbine-torque-dev
Subject:    [jira] [Commented] (TORQUE-320) GroupBy adds columns to the select clause
From:       "Thomas Vandahl (JIRA)" <jira () apache ! org>
Date:       2014-08-17 18:55:18
Message-ID: JIRA.12727919.1405602216528.17628.1408301718275 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/TORQUE-320?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=14100054#comment-14100054 ] 

Thomas Vandahl commented on TORQUE-320:
---------------------------------------

My point just was that I remember especially Oracle barking on me because the column \
used in the GROUP BY clause was not listed in the selected columns. I don't know when \
this happens, it might be a totally unrelated case. You have much more Oracle \
experience than I. In my case the different methods would not have helped much \
because it's the database that throws the error. 

I just wanted to make sure that Torque does not create invalid SQL for some DBs. I'm \
unhappy with the ILIKE operator already.

> GroupBy adds columns to the select clause
> -----------------------------------------
> 
> Key: TORQUE-320
> URL: https://issues.apache.org/jira/browse/TORQUE-320
> Project: Torque
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 4.0
> Reporter: Thomas Fox
> 
> If I create a Criteria, define the select columns manually and then add groupBy \
> Columns, SqlBuilder adds the groupBy Columns to the select columns One should be \
> able to create GROUP BY Queries without adding the columns to the select clause



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]