[Date Prev][Date Next]
RE: Paged results flakey - and hdb vs bdb
Does that mean that if the sizelimit is 500 in the server config file, I will not be able to page through more than 500 entries, even if my page size is 100?
Or does that mean when I do my search, if I set the size limit on my search controls object, it will limit the sum of the pages to that limit?
I hope it is #2 - that it doesn't limit by the sizelimit in the conf file - this would make the sizelimit useless to us - we would have to set it insanely high, and then one bad query can knock out the server. Currently, we set the conf file limit to a low number, to keep bad queries from killing the server, but with paged results, we can still iterate across all of the entries in a large query.
I'll try to find some time today or tomorrow to try out the code in HEAD.
From: Pierangelo Masarati [mailto:firstname.lastname@example.org]
Sent: Tuesday, April 13, 2004 9:07 AM
To: Armbrust, Daniel C.
Subject: RE: Paged results flakey - and hdb vs bdb
> I'll take this one back - and chalk it up to using old software.
> I can't currently recreate this error with version 2.2.7, so I'm going
> to assume it is fixed.
About this first issue, could you do us a favor? The paged results code
was changed recently in HEAD code, and is not released yet. I would
appreciate if you could give it a try. The cahnges were mostly in search
limits handling, which now span the entire range and not one single page
as it used to be. You'll find a thread about this starting from
The essential idea is that a size limit set from the server side is
honored considering the whole scope of the search, regardless of its
results being paged or not. I'd like to have some feedback about it
because I might have not been able to try all the possible combinations of
settings. If there are any issues, please use the ITS to keep tgrack of