Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Use < instead of < in the r-tree documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
a55027b4525f9751e3b90a8c09d676f7 |
User & Date: | drh 2016-08-27 23:54:56.852 |
Context
2016-08-29
| ||
11:56 | Updates to TH3 documentation. (check-in: 8bc0546bb6 user: drh tags: trunk) | |
2016-08-27
| ||
23:54 | Use < instead of < in the r-tree documentation. (check-in: a55027b452 user: drh tags: trunk) | |
2016-08-25
| ||
19:50 | Update documentation for the sqldiff tool to include the --vtab option. (check-in: 0e6ed0fa48 user: dan tags: trunk) | |
Changes
Changes to pages/rtree.in.
︙ | ︙ | |||
172 173 174 175 176 177 178 | you can efficiently do inequality queries against the coordinate ranges. ^(To find all elements of the index that are contained within the vicinity of Charlotte, North Carolina, one might do: </p> <blockquote><pre> SELECT id FROM demo_index | | | | | | | 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 | you can efficiently do inequality queries against the coordinate ranges. ^(To find all elements of the index that are contained within the vicinity of Charlotte, North Carolina, one might do: </p> <blockquote><pre> SELECT id FROM demo_index WHERE minX>=-81.08 AND maxX<=-80.58 AND minY>=35.00 AND maxY<=35.44; </pre></blockquote>)^ <p> ^The query above would very quickly locate the id of 1 even if the R*Tree contained millions of entries. The previous is an example of a "contained-within" query. The R*Tree also supports "overlapping" queries. ^(For example, to find all bounding boxes that overlap the Charlotte area: </p> <blockquote><pre> SELECT id FROM demo_index WHERE maxX>=-81.08 AND minX<=-80.58 AND maxY>=35.00 AND minY<=35.44; </pre></blockquote>)^ <p> ^(This second query would find both entry 1 (the SQLite.org office) which is entirely contained within the query box and also the 12th Congressional District which extends well outside the query box but still overlaps the query box.)^ </p> <p> ^Note that it is not necessary for all coordinates in an R*Tree index to be constrained in order for the index search to be efficient. ^(One might, for example, want to query all objects that overlap with the 35th parallel: </p> <blockquote><pre> SELECT id FROM demo_index WHERE maxY>=35.0 AND minY<=35.0; </pre></blockquote>)^ <p> But, generally speaking, the more constraints that the R*Tree module has to work with, and the smaller the bounding box, the faster the results will come back. </p> |
︙ | ︙ | |||
289 290 291 292 293 294 295 | the North Carolina 12th District, one may be to run a query like this: </p> <blockquote><pre> SELECT objname FROM demo_data, demo_index WHERE demo_data.id=demo_index.id AND contained_in(demo_data.boundary, :boundary) | | | | 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 | the North Carolina 12th District, one may be to run a query like this: </p> <blockquote><pre> SELECT objname FROM demo_data, demo_index WHERE demo_data.id=demo_index.id AND contained_in(demo_data.boundary, :boundary) AND minX>=-81.0 AND maxX<=-79.6 AND minY>=35.0 AND maxY>=36.2; </pre></blockquote>)^ <p>In the query above, one would presumably bind the binary BLOB description of the precise boundary of the 12th district to the ":boundary" parameter.</p> <p>Notice how the query above works: The R*Tree index runs in the outer |
︙ | ︙ |