https://bugzilla.wikimedia.org/show_bug.cgi?id=39936
--- Comment #10 from Daniel Kinzler <[email protected]> 2012-09-26 08:39:22 UTC --- (In reply to comment #9) > However I don't think we need an extra parameter for the api to throw an error > instead of truncating when there are too many values. Right: it should *always* throw an error. Not that this issue is far more severe for queries that update data - in that case, it causes silent data loss. That's what caused john to file the initial report. > As we've seen, you can query the api (userinfo, paraminfo) for your current > limit and split the request if needed into chunks of the correct size. For that to work, the client needs a way to even determine that limit. I don't think there's currently any reliable way to do that. > Even if you don't want to do that, you can count the results you got and > continue requesting if got over the limit - I did that once when getting > paraminfo for *all* querymodules :-) So... that would basically be a paging mechanism. Orthogonal to the existing paging mechanism. I think that can get pretty confusing... -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
