Grails

totalCount throws error when order is specified

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0-RC2
  • Fix Version/s: None
  • Component/s: Persistence
  • Environment:
    OS X

Description

An error is thrown whenever totalCount is called on a criteria object and order is specified either as a default sort order in the GORM mapping or if order is specified in the criteria itself. An error like the following is thrown:

Column "THIS_.DATE_CREATED" must be in the GROUP BY list; SQL statement: select count as y0_ from post this_ order by this_.date_created desc limit ?

I've attached a sample project that shows this behavior with a criteria object. To reproduce this error, add two new Post objects and view the list to see the error.

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. GRAILS-8365 totalCount creates additional order by statement

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

Activity

Hide
Permalink
Craig Burke added a comment -

Hi Jeff,

I'm not sure this is actually a duplicate. This is different than the issue in RC1. In RC2 it actually throws an error instead of just returning an incorrect count.

Show
Craig Burke added a comment - Hi Jeff, I'm not sure this is actually a duplicate. This is different than the issue in RC1. In RC2 it actually throws an error instead of just returning an incorrect count.

People

  • Assignee:
    Jeff Brown
    Reporter:
    Craig Burke
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: