Re: [Hibernate] adding Criteria.count() method

[Greg H. <not...@ya...>]

Last time I checked it was 12 votes and there already is a patch. ;)
However, what's the point of using a patch that will be more of a
problem to maintain and have to keep patching on each new version than
a deprecated API?

You may not want the API to go that way and that's fine, but it's been
quite a while since requests started coming in for this kind of
functionality and how it can be implemented or accomplished isn't
nearly as important in my mind as whether or not it will be.

If the team genuinely intends to eventually implement "something"
whereby the effect of finding a count could be created then people can
look at the road map and decide whether or not they can wait for it. 
But, the impression I get (especially from comments such as
Christian's) is that it will never be possible to find out how many
objects could be retrieved without actually retrieving them or writing
a whole lot of "throw-away" code.

What "really" sucks, is having to load 100 times as many objects as you
wanted just to find out how many exist.  Even if you use "light-weight"
objects this still sucks.

My 2 cents.

--- Emmanuel Bernard <emm...@hi...> wrote:
> 
> > Christian Bauer wrote:
> >
> >> On 26 Feb (17:14), Fu Gui wrote:
> >>
> >>  
> >>
> >>> Why do we not fix and close it?  Votes:11, it is a large number
> in 
> >>> jira.
> >>>   
> >>
> >>
> >> Because it sucks.
> >>
> >>  
> >>
> > And in a more diplomatic way. We've the feeling this is not the way
> 
> > the API should be. We're thinking on a better API. The worst
> scenario 
> > would be to have to deprecate a sucking API becauseof not having
> > take the time to think.
> >
> > Be patient, and enjoy the power of open source, you're 11 that need
> > this feature right now, it'll be easy to work together and supply 
> > patch until we're ready :)
> >


__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools