| commit | 2ecd7f8d12e07bca7777e64bba0595e0ab34832d | |
| author | Olly Betts <olly@survex.com> | |
| Wed, 22 Nov 2017 21:34:52 +0000 (23 10:34 +1300) | ||
| committer | Olly Betts <olly@survex.com> | |
| Wed, 22 Nov 2017 21:44:45 +0000 (23 10:44 +1300) | ||
| tree | 76633878222db0810bb3f9b5264f69ac2383a824 | treesnapshot (tar.gz zip) |
| parent | 4c90899dfe3b1131abddfc5b289184a0d1bcdf3e | commitdiff |
Fix clamping of maxitems and time limit handling
The maxitems argument to get_mset() was internally clamped to
db.get_doccount() - corrected to db.get_doccount() - first. In
practice this doesn't actually seem to cause any issues.
When the match time limit expires, clamp check_at_least to
first + maxitems instead of to maxitems. In practice this also
doesn't seem to actually cause any issues (at least I've failed to
construct a testcase where it actually makes an observable difference).
The maxitems argument to get_mset() was internally clamped to
db.get_doccount() - corrected to db.get_doccount() - first. In
practice this doesn't actually seem to cause any issues.
When the match time limit expires, clamp check_at_least to
first + maxitems instead of to maxitems. In practice this also
doesn't seem to actually cause any issues (at least I've failed to
construct a testcase where it actually makes an observable difference).
| xapian-core/api/enquire.cc | diffblobblamehistory | |
| xapian-core/matcher/multimatch.cc | diffblobblamehistory |