Derek Atkins writes:
>
> An alternative approach: add to the Query object a "max return" value,
> so that a client can set the 'max number of Splits to return'. Then
> we don't necessarily need two RPCs; perhaps the Query RPC can return
> the actual number of matching splits, even though it only returns the
> max number. The only question would be _which_ "max results" should
> get returned? ;)
In fact, such a value already exists:
xaccQuerySetMaxSplits(Query * q, int n)
sets the maximum number of splits to return. Currently, if the total
number that would be returned exceeds n, then the 'last' n are returned,
where 'last' is defined by the sorting method used for that Query.
dave
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel