You are viewing a single comment's thread from:
RE: Steem for script kiddies: paginated get_account_history calls
Now I tested the script and the api. As we have already discovered, the pagination is a little irritating. Because limit+1 records is returned instead of limit records, you have to be careful with the pagination... or set limit=(real)limit-1 in the request.
However, it is very confusing that the number of data records in the response should not be more than limit due to the loop termination condition.
For rocksdb, maybe it's here? Which (I think) goes here?
The github issue said:
I still don't understand why it works the way it does, though. Maybe an off by one error in this loop?
And/Or maybe this should be > instead of >= ?
I'd need to step through it line by line to understand, but I'm not that curious. ;-)