Re: limitation on XML-RPC result size? experiencing incomplete result sets

> Is there an inherent limit on records contained in or other implicit
> filtering applied to the result set returned to an XML-RPC query?

This limit is set on the server;  obviously generating a massive  
result set would be a bad thing.

The limit applied is specified by the LSMaxSearchCount default;  which  
I think defaults to 100.

There is also, I beleive, an internal limit set in the logic layer via  
the "LSDBFetchRelationCommand_MAX_SEARCH_COUNT" default;  but I'm not  
certain how that one is applied.

> However, 1560250 does not appear in any of these statements, even
> though it was returned by the first query. It seems that ogo-xmlrpcd

Yep, this looks like typical xmlrpcd/DocumentAPI behaviour;  first it  
finds qualified objects and then it marshals them until it hits the  
limit.

> effectively ignores this company_id (among others.) Has it been
> filtered somehow or the result set truncated?

My guess in truncated

> Is there a relevant
> configuration setting which could explain the difference between the
> two OGo installations? Incidentally, this company_id does not show up
> in the results of an equivalent fetchIds() XML-RPC request either.

Did you have a limit set on your old server?

--
OpenGroupware.org XML-RPC
xmlrpc@xxxxxxxxxxxxxxxxx
http://mail.opengroupware.org/mailman/listinfo/xmlrpc