Documentation Source Text

Check-in [c0722042ac]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Deprecate the SQLITE_RTREE_INT_ONLY compile-time option.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: c0722042ac3ec04ff3286c90c82466d2af039421538a50bf6eaccb0972274f3f
User & Date: drh 2017-10-24 12:47:55
Context
2017-10-24
14:54
Update the speed and size graphs. check-in: c674dc0ada user: drh tags: trunk
12:47
Deprecate the SQLITE_RTREE_INT_ONLY compile-time option. check-in: c0722042ac user: drh tags: trunk
2017-10-21
20:59
New updates to the change log for the 3.21.0 release. check-in: 9654c88db8 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/compile.in.

1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
}

COMPILE_OPTION {SQLITE_ENABLE_STMTVTAB} {
  This compile-time option enables the [SQLITE_STMT virtual table] logic.
}

COMPILE_OPTION {SQLITE_RTREE_INT_ONLY} {
  If this option is used together with [SQLITE_ENABLE_RTREE] then the
  [rtree | R*Tree extension] will only store 32-bit signed integer
  coordinates and all internal computations will be done using integers
  instead of floating point numbers.
}

COMPILE_OPTION {SQLITE_ENABLE_SQLLOG} {
  This option enables extra code (especially the [SQLITE_CONFIG_SQLLOG]
  option to [sqlite3_config()]) that can be used to create logs of all
  SQLite processing performed by an application.  These logs can be useful
  in doing off-line analysis of the behavior of an application, and especially







|
<
<
<







1014
1015
1016
1017
1018
1019
1020
1021



1022
1023
1024
1025
1026
1027
1028
}

COMPILE_OPTION {SQLITE_ENABLE_STMTVTAB} {
  This compile-time option enables the [SQLITE_STMT virtual table] logic.
}

COMPILE_OPTION {SQLITE_RTREE_INT_ONLY} {
  This compile-time option is deprecated and untested.



}

COMPILE_OPTION {SQLITE_ENABLE_SQLLOG} {
  This option enables extra code (especially the [SQLITE_CONFIG_SQLLOG]
  option to [sqlite3_config()]) that can be used to create logs of all
  SQLite processing performed by an application.  These logs can be useful
  in doing off-line analysis of the behavior of an application, and especially

Changes to pages/rtree.in.

336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
<blockquote><pre>
CREATE VIRTUAL TABLE intrtree USING rtree_i32(id,x0,x1,y0,y1,z0,z1);
</pre></blockquote>

<p>
An rtree_i32 stores coordinates as 32-bit signed integers.  But it still
using floating point computations internally as part of the r-tree algorithm.
For applications running on processors without hardware floating point,
it might be desirable to have a pure integer implementation of r-trees.
This is accomplished by compiling with the [SQLITE_RTREE_INT_ONLY] option.
When SQLITE_RTREE_INT_ONLY is used, both the "rtree" and the "rtree_i32"
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.







<
<
<
<
<
<







336
337
338
339
340
341
342






343
344
345
346
347
348
349
<blockquote><pre>
CREATE VIRTUAL TABLE intrtree USING rtree_i32(id,x0,x1,y0,y1,z0,z1);
</pre></blockquote>

<p>
An rtree_i32 stores coordinates as 32-bit signed integers.  But it still
using floating point computations internally as part of the r-tree algorithm.







<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.