I fail to see how the paged search control provides the same thing. Using a paged search control with 25+million entries would take forever.
The people are not looking for the "count" of entries returned but rather the number of entries contained within the containers. This particular request is to monitor counts within the directory and nothing about any page display. ᐧ -- -jim Jim Willeke On Thu, Dec 11, 2014 at 8:58 AM, Emmanuel Lécharny <[email protected]> wrote: > Le 11/12/14 14:33, Jim Willeke a écrit : > > But in "real-life", usually, entry types are typically broken into > > containers on at least a broad basis like: > > > > ou=People, dc=willeke,dc=com > > ou=groups, dc=willeke,dc=com > > I would question the need of such request, when it's about requesting > the number of resulting entries. > > I saw that *many* times in a previous SQL life, where people designing > GUI were doing a COUNT(*) to get the number of returned elements, in > order to design a page with arrows if this number is above a given > number : this is uterly STUPID. Doing so results in the request being > done twice on the SQL database. Enough said that all the SQL database > provide a cursored system, which allows the GUI developper to know when > to expose those arrows, without having to send two requests. > > In LDAP, I don't see that being different : the Paged Search control > offer the exact same service. > >
