The reason why I don't need the "group by" column in my SELECT is because I'm going to use it as a subquery (DetachedCriteria). I need a single column SELECT so I could use the result of this subquery in the IN statement of the main query.
On Dec 19, 10:38 am, "Will Shaver" <[email protected]> wrote: > Why do you need to be rid of the group by column in your results? It should > not adversely affect your query performance by a huge margin. The result > order can be maintained through adding order by to the query. It may be > possible to hack the source so as to add a GroupByButDontSelect() method of > some sort, but for what end? > I wrote the existing group by code for the criteria queries (last I checked > it still doesn't exist in Hibernate). It might not be too bad to add in a > boolean for actually selecting it or not, I'm not sure as it has been > several months since I've reviewed that section of code. > > -Will > > On Fri, Dec 19, 2008 at 7:57 AM, Fabio Maulo <[email protected]> wrote: > > 2008/12/19 alex <[email protected]> > > >> Another reason for using Criteria API is Resharper and intellisense. > > > well... you have the problem and I hope you can solve it soon in your way. > > I did myyyyy waaaaay! (as said THE VOICE) > > -- > > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
