Rob van Maris <[EMAIL PROTECTED]> wrote: > > <[EMAIL PROTECTED]:> > > On Mon, 2002-10-14 at 12:04, Rob van Maris wrote: > > > - It should not throw an exception, but just truncate the results and > log a > > > warning - isn't this what warnings are for? > > Warnings to users should be given to users, warings for administrators > > should be given to administrators. > > I think that you could read for users jsp-exceptions in pages and for > > administrators errors in the log. > > Personally i think that there is already far to much user information > > inside the log, but maybe there are people who have a different view > > about this... > > When a resultset is so large it has to be truncated, the problem lies > principally in the originating code (or jsp). A warning in the log is useful > in such a situation, since it draws the administrators attention to the > problem in order to correct the problem. > The end-user, on the other hand, should not be bothered with this. If the > database query results from input entered by end-users, resultset overflow > can usually be prevented by proper validation of the input parameters (i.e. > a minimum length of search terms in a text search).
I agree. But the situation is practicly even worse. Because IIRC even if the jsp limits the size of the result (<mm:listnodes max="10" offset="10" />), still the limitless query is done, and the entire resultset read. So I do think that it must be possible to apply a maximum, and the 'max' attribute should as soon as the infrastructure in the core is present for this, actually limit the query. Michiel -- Michiel Meeuwissen Mediapark, C 107 tel. +31 (0)35 6772979
