| commit | f3cf8dabcec3da027a2f5e4d356adadbef6b528f | [log] [tgz] |
|---|---|---|
| author | Dave Borowitz <dborowitz@google.com> | Mon Jan 12 16:25:10 2015 -0800 |
| committer | Dave Borowitz <dborowitz@google.com> | Tue Jan 13 17:14:16 2015 -0800 |
| tree | 8d08e1f051d3292d63b93cdde426b27a18525e8e | |
| parent | 07c71df19df75857ada7e38ff3d9f80acbfbe90b [diff] |
QueryProcessor: Don't overflow limit This allows us to use Integer.MAX_VALUE as a sentinel to return as many results as possible. This actually causes a new bug whereby a limit of MAX_VALUE will never return true for moreChanges(), but that should be hard to hit in practice. Change-Id: I8b2f0e0e7a2740da110505867f51d0f82397351d