]> git.ipfire.org Git - thirdparty/sqlite.git/commit
When a floating-point RTREE is presented with large integer constraints -
authordrh <>
Mon, 22 May 2023 16:35:21 +0000 (16:35 +0000)
committerdrh <>
Mon, 22 May 2023 16:35:21 +0000 (16:35 +0000)
commit0503cd6d11211a6b549194f248b1f9fb76e080d8
tree0c00cdf58403a0e1c88fc5162cdd11582576c7cc
parentb838a229be26ffb08bf2c221e040103438724074
When a floating-point RTREE is presented with large integer constraints -
integers that are too big to be represented exactly by a float - then take
extra steps to ensure that all possibly relevant entries in the RTREE are
returned, even in boundary cases.  Fix for the problem identified by
[forum:/forumpost/da70ee0d0d|forum post da70ee0d0d].

FossilOrigin-Name: bfd8d9100015f3e3fb011698963d670bd89b64ec8a8ab931e0c6c3076b029377
ext/rtree/rtree.c
ext/rtree/rtree1.test
manifest
manifest.uuid