Arjan Lamers wrote: > We are still running 1.7.0 because MMBase 1.7.0 and 1.7.1 are too > incompatible in my experience for an easy transition. This bug is fixed > in 1.7.1?
In 1.7.2. I meant bug #6612. > Then I probably have a new bug for 1.7.1 if the node-by-node checking is > enabled: what if the original query is limited (in our case we limit the > number of news items to 3 on the homepage). If any of the first 3 news > items resulting from the query are not readable for the user the result > will not be 3, even if there are more than 3 news items which he is > allowed to see. (Not tested though) Yes, that may be a problem. Max and also count may not work absolutely right then. It should probably detect that it throwed away some, and do a new query, to fetch some more. AFAIK this last behaviour is not implemented. Another correct sollution would be to also drop the 'max' on the query if it is 'unchecked', but I doubt if you want that.. > > Why is there a context limit anyway? Is it to avoid the max entries in > an "IN" statement in the database? Yes. Or to avoid hitting a maximal length of the SQL query, which applies sometimes IIRC. Your solution of simply increasing this limit is the right one, if it works. If you hit a maximum for the query length, then I'd say you security configuration is actually too complicated for the powers of your database... Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
