Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Clarification of a sentence in the R-Tree documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
96728cbc1323dbc74b3502d5f745487e |
| User & Date: | drh 2017-02-08 18:10:25.724 |
Context
|
2017-02-09
| ||
| 19:48 | Final adjustments to the change log before starting release tests. (check-in: b6f0b02c8c user: drh tags: trunk) | |
|
2017-02-08
| ||
| 18:10 | Clarification of a sentence in the R-Tree documentation. (check-in: 96728cbc13 user: drh tags: trunk) | |
|
2017-02-04
| ||
| 16:22 | Update the preformance spreadsheet (check-in: 49eb6735bf user: drh tags: trunk) | |
Changes
Changes to pages/rtree.in.
| ︙ | ︙ | |||
347 348 349 350 351 352 353 |
virtual tables store 32-bit integers and only integer values are used for
internal computations.
<tcl>hd_fragment {customquery} {custom r-tree queries}</tcl>
<h1>Custom R-Tree Queries</h1>
<p>By using standard SQL expressions in the WHERE clause of a SELECT query,
| | | | 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 |
virtual tables store 32-bit integers and only integer values are used for
internal computations.
<tcl>hd_fragment {customquery} {custom r-tree queries}</tcl>
<h1>Custom R-Tree Queries</h1>
<p>By using standard SQL expressions in the WHERE clause of a SELECT query,
a programmer can query for all R*Tree entries that
intersect with or are contained within a particular bounding-box.
Custom R*Tree queries, using the MATCH
operator in the WHERE clause of a SELECT, allow the programmer to query for
the set of R*Tree entries that intersect any arbitrary region or shape, not
just a box. This capability is useful, for example, in computing the
subset of objects in the R*Tree that are visible from a camera positioned
in 3-D space.
|
| ︙ | ︙ |