Bug #3400

Updated by Peter Amstutz about 6 years ago

If a developer writes something like @Link.where(...).each do { ... }@ and the API call results in more than the result limit (default 100), the code will only iterate over the first 100 results. This is error prone and leads to subtle bugs where code works as expected when there are less than 100 results but suddenly starts losing results when there are more than 100 results. The client SDKs should clearly distinguish between cases where paging is desired vs iterating over the entire result set. This problem currently exists in all client SDKs, including Python, Go, Ruby, command line, and Workbench.