Flutterby™! : Unintended Consequences

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Unintended Consequences

2012-09-06 00:41:11.154284+02 by Dan Lyke 2 comments

Unintended Consequences: API hardcoded limit of 200 results was about to push me to do 2000+ individual queries instead.

comments in descending chronological order (reverse):

#Comment Re: made: 2012-09-06 22:09:18.068022+02 by: Dan Lyke

Yeah, running some numbers a 20meg result set is kinda big, but I'm not sure that me hitting the thing two thousand times in a row would have been better. In the end we ran the query by hand.

#Comment Re: made: 2012-09-06 01:41:19.141781+02 by: meuon

ill agree with the 200 limit for most apis. it depends. we often limit to 50. if the backend does something heavy, you do not want some crappy input parameters bogging down a system, or dumping data it should not.

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.