Another problem with having to specify the HAVING in the group key..
is that it looks like it would lead to errors when sequencing multiple
named_scopes, i.e.:
Thank you.. I was guessing about it since your first post.. now I
just hobe rail 2.3 won't brake too much things, it's never good to
have to switch framework version in the middle of an app development!
Hmmmm! Even worse... named_scopes completely skip the :order key if
there's a HAVING clause.. °_° I thought I could have used wht I
proposed at 13:00, but the named scope didn't used the group key at
all to find the resultset... sic...
Quite annoying, I'm really hoping 2.3 won't break too much
compatibility with 2.2.2 code..