Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Changes In Branch branch-3.24-https Excluding Merge-Ins
This is equivalent to a diff from 27b8057665 to 59e5f9e3da
2018-06-09
| ||
22:13 | Fix typos in the compile.html page. (check-in: 10c05df9fb user: drh tags: branch-3.24) | |
2018-06-08
| ||
13:21 | Use https for all internal hyperlinks. (Leaf check-in: 59e5f9e3da user: drh tags: branch-3.24-https) | |
2018-06-05
| ||
23:20 | Clarification that the overwrite optimization does not affect the behavior of triggers. (check-in: 27b8057665 user: drh tags: branch-3.24) | |
2018-06-04
| ||
19:41 | Add the upsert-clause.gif image. (check-in: 7d927bcea1 user: drh tags: trunk) | |
Changes to pages/about.in.
︙ | |||
77 78 79 80 81 82 83 | 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 | - - + + | even if interrupted by system crashes or power failures. All of this is verified by the automated tests using special test harnesses which simulate system failures. Of course, even with all this testing, there are still bugs. But unlike some similar projects (especially commercial competitors) SQLite is open and honest about all bugs and provides |
︙ |
Changes to pages/affcase1.in.
︙ | |||
236 237 238 239 240 241 242 | 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 | - + | Surprisingly, using SQLite in place of ZIP makes the presentation file smaller. Really. One would think that a relational database file would be larger than a ZIP archive, but at least in the case of NeoOffice that is not so. The following is an actual screen-scrape showing the sizes of the same NeoOffice presentation, both in its original ZIP archive format as generated by NeoOffice (self2014.odp), and as repacked as an SQLite database using the |
︙ |
Changes to pages/amalgamation.in.
︙ | |||
149 150 151 152 153 154 155 | 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 | - + - + | <p>In both cases, the split amalgamation can be obtained by substituting "sqlite3-all.c" for "sqlite3.c" as the make target. <h2>Dependencies</h2> <p>The build process makes extensive use of the |
Changes to pages/appfileformat.in.
︙ | |||
277 278 279 280 281 282 283 | 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 | - - + + | <p>SQLite is transactional, meaning that multiple changes can be grouped together such that either all or none of them occur, and so that the changes can be rolled back if a problem is found prior to commit. This allows an application to make a change incrementally, then run various sanity and consistency checks on the resulting data prior to committing the changes to disk. The |
︙ |
Changes to pages/asyncvfs.in.
︙ | |||
118 119 120 121 122 123 124 | 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 | - + | <h2>2.0 COMPILATION AND USAGE</h2> <p> The asynchronous IO extension consists of a single file of C code (sqlite3async.c), and a header file (sqlite3async.h), located in the |
︙ | |||
144 145 146 147 148 149 150 | 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 | - + | sqlite3async_run(). <li><p>Use the normal SQLite API to read and write to databases via the asynchronous IO VFS. </ol> <p>Refer to comments in the |
︙ |
Changes to pages/books.in.
︙ | |||
286 287 288 289 290 291 292 | 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 | - + | <p>SQLite is a small, zero-configuration, custom-tailored, embeddable, thread-safe, easily maintainable, transaction-oriented, SQL-based, relational database management system. There is no separate install or setup procedure to initialize SQLite before using it. There is no configuration file. SQLite is open source, and is available in the public domain (for more information on open source, visit http://opensource.org). |
︙ |
Changes to pages/changes.in.
1 2 3 4 5 6 7 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | - - - - + + + + | <title>Release History Of SQLite</title> <tcl>hd_keywords {release history} {complete list of SQLite releases}</tcl> <h1 align=center>Release History</h1> <p> This page provides a high-level summary of changes to SQLite. For more detail, see the Fossil checkin logs at |
︙ | |||
1328 1329 1330 1331 1332 1333 1334 | 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 | - + | to 100 pages. Yields about a 5% performance increase on common workloads. <li>Miscellaneous micro-optimizations result in 22.3% more work for the same number of CPU cycles relative to the previous release. SQLite now runs twice as fast as [version 3.8.0] and three times as fast as [version 3.3.9]. (Measured using [http://valgrind.org/docs/manual/cg-manual.html|cachegrind] on the |
︙ | |||
1537 1538 1539 1540 1541 1542 1543 | 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 | - + - + | chng {2014-11-18 (3.8.7.2)} { <li>Enhance the [ROLLBACK] command so that pending queries are allowed to continue as long as the schema is unchanged. Formerly, a ROLLBACK would cause all pending queries to fail with an [SQLITE_ABORT] or [SQLITE_ABORT_ROLLBACK] error. That error is still returned if the ROLLBACK modifies the schema. <li>Bug fix: Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. |
︙ | |||
1569 1570 1571 1572 1573 1574 1575 | 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 | - + | chng {2014-10-17 (3.8.7)} { <p><b>Performance Enhancements:</b> <li>Many micro-optimizations result in 20.3% more work for the same number of CPU cycles relative to the previous release. The cumulative performance increase since [version 3.8.0] is 61%. (Measured using [http://valgrind.org/docs/manual/cg-manual.html|cachegrind] on the |
︙ | |||
1594 1595 1596 1597 1598 1599 1600 | 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 | - + - + - + - + - + | [sqlite3_result_text64()]. <li>Added the new interface [sqlite3_msize()] that returns the size of a memory allocation obtained from [sqlite3_malloc64()] and its variants. <li>Added the [SQLITE_LIMIT_WORKER_THREADS] option to [sqlite3_limit()] and [PRAGMA threads] command for configuring the number of available worker threads. <li>The [spellfix1] extension allows the application to optionally specify the rowid for each INSERT. |
︙ | |||
1639 1640 1641 1642 1643 1644 1645 | 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 | - + | error from 1 second to 10 seconds. <li>Added the [likely(X)] SQL function. <li>The [unicode61] tokenizer is now included in [FTS4] by default. <li>Trigger automatic reprepares on all prepared statements when [ANALYZE] is run. <li>Added a new [loadable extension] source code file to the source tree: |
︙ | |||
1661 1662 1663 1664 1665 1666 1667 | 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 | - + - + - + - + - + | <li>Ensure that the query planner never tries to use a self-made transient index in place of a schema-defined index. <li>Other minor tweaks to improve the quality of [VDBE] code. <p><b>Bug Fixes:</b> <li>Fix a bug in [CREATE INDEX|CREATE UNIQUE INDEX], introduced when [WITHOUT ROWID] support added in version 3.8.2, that allows a non-unique NOT NULL column to be given a UNIQUE index. |
︙ | |||
1706 1707 1708 1709 1710 1711 1712 | 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 | - + - + - + - + - + - + - + - + - + - + - + | Similarly optimize "x NOT IN (?)" <li>Add the ".system" and ".once" commands to the [command-line shell]. <li>Added the [SQLITE_IOCAP_IMMUTABLE] bit to the set of bits that can be returned by the xDeviceCharacteristics method of a [VFS]. <li>Added the [SQLITE_TESTCTRL_BYTEORDER] test control. <p><b>Bug Fixes:</b> <li>OFFSET clause ignored on queries without a FROM clause. |
︙ | |||
1786 1787 1788 1789 1790 1791 1792 | 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 | - + - + - + - + - + - + - + | <li>Change the datatype of SrcList.nSrc from type u8 to type int to work around an issue in the C compiler on AIX. <li>Get extension loading working on Cygwin. <li>Bug fix: Fix the [char()] SQL function so that it returns an empty string rather than an "out of memory" error when called with zero arguments. <li>Bug fix: DISTINCT now recognizes that a [zeroblob] and a blob of all 0x00 bytes are the same thing. |
︙ | |||
1920 1921 1922 1923 1924 1925 1926 | 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 | - + | <li>The directory used to hold temporary files on unix can now be set using the SQLITE_TMPDIR environment variable, which takes precedence over the TMPDIR environment variable. The [sqlite3_temp_directory] global variable still has higher precedence than both environment variables, however. <li>Added the [PRAGMA stats] statement. <li><b>Bug fix:</b> Return the correct answer for "SELECT count(*) FROM table" even if there is a [partial index] on the table. Ticket |
︙ | |||
2049 2050 2051 2052 2053 2054 2055 | 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 | - + - + - + - + - + - + - + - + - + - + - + - + - + | <li>Discontinue the use of posix_fallocate() on unix, as it does not work on all filesystems. <li>Improved tracing and debugging facilities in the Windows [VFS]. <li>Bug fix: Fix a potential <b>database corruption bug</b> in [shared cache mode] when one [database connection] is closed while another is in the middle of a write transaction. |
︙ | |||
2163 2164 2165 2166 2167 2168 2169 | 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 | - + - + - + | <li>Enhance the [spellfix1] extension so that the edit distance cost table can be changed at runtime by inserting a string like 'edit_cost_table=TABLE' into the "command" field. <li>Bug fix: repair a long-standing problem that could cause incorrect query results in a 3-way or larger join that compared INTEGER fields against TEXT fields in two or more places. |
︙ | |||
2312 2313 2314 2315 2316 2317 2318 | 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 | - + | <li>SQLITE_SOURCE_ID: "2012-06-11 02:05:22 f5b5a13f7394dc143aa136f1d4faba6839eaa6dc" <li>SHA1 for sqlite3.c: ff0a771d6252545740ba9685e312b0e3bb6a641b } chng {2012-05-22 (3.7.12.1)} { <li>Fix a bug |
︙ | |||
2352 2353 2354 2355 2356 2357 2358 | 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 | - + - + | <li>Improved optimization of aggregate subqueries contained within an aggregate query. <li>Bug fix: Fix the [RELEASE] command so that it does not cancel pending queries. This repairs a problem introduced in 3.7.11. <li>Bug fix: Do not discard the DISTINCT as superfluous unless a subset of the result set is subject to a UNIQUE constraint <em>and</em> it none of the columns in that subset can be NULL. |
︙ | |||
2382 2383 2384 2385 2386 2387 2388 | 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 | - + | <li>Added support for the [FTS4 languageid option]. <li>Documented support for the [FTS4 content option]. This feature has actually been in the code since [version 3.7.9] but is only now considered to be officially supported. <li>Pending statements no longer block [ROLLBACK]. Instead, the pending statement will return SQLITE_ABORT upon next access after the ROLLBACK. <li>Improvements to the handling of CSV inputs in the [command-line shell] |
︙ | |||
2446 2447 2448 2449 2450 2451 2452 | 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 | - + - + - + | [SQLITE_ENABLE_TREE_EXPLAIN] compile-time option to enable the [command-line shell] to display ASCII-art parse trees of SQL statements that it processes, for debugging and analysis. <li><b>Bug fix:</b> Add an additional xSync when restarting a WAL in order to prevent an exceedingly unlikely but theoretically possible database corruption following power-loss. |
︙ | |||
2524 2525 2526 2527 2528 2529 2530 | 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 | - + | indices in a WHERE clause. <li> SQLITE_SOURCE_ID: "2011-09-19 14:49:19 3e0da808d2f5b4d12046e05980ca04578f581177" <li> SHA1 for sqlite3.c: bfcd74a655636b592c5dba6d0d5729c0f8e3b4de } chng {2011-06-28 (3.7.7.1)} { |
︙ | |||
2616 2617 2618 2619 2620 2621 2622 | 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 | - + | [SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL] options for the [sqlite3_db_status()] interface. <li> Added the [SQLITE_OMIT_AUTORESET] compile-time option. <li> Added the [SQLITE_DEFAULT_FOREIGN_KEYS] compile-time option. <li> Updates to [sqlite3_stmt_readonly()] so that its result is well-defined for all prepared statements and so that it works with [VACUUM]. <li> Added the "-heap" option to the [command-line shell] |
︙ | |||
2653 2654 2655 2656 2657 2658 2659 | 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 | - + | to the FTS [matchinfo()] function. <li> Added the test_superlock.c module which provides example code for obtaining an exclusive lock to a rollback or WAL database. <li> Added the test_multiplex.c module which provides an example VFS that provides multiplexing (sharding) of a DB, splitting it over multiple files of fixed size. |
︙ | |||
2686 2687 2688 2689 2690 2691 2692 | 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 | - + | the VDBE provides hints to the B-Tree layer letting the B-Tree layer know when it is safe to use hashing instead of B-Trees for transient tables. <li> Miscellaneous documentation enhancements. } chng {2010-08-24 (3.7.2)} { |
︙ | |||
2713 2714 2715 2716 2717 2718 2719 | 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 | - + | <li> The SQLITE_MAX_PAGE_SIZE compile-time option is now silently ignored. The maximum page size is hard-coded at 65536 bytes. } chng {2010-08-04 (3.7.0.1)} { <li> Fix a potential database corruption bug that can occur if version 3.7.0 and version 3.6.23.1 alternately write to the same database file. |
︙ | |||
2801 2802 2803 2804 2805 2806 2807 | 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 | - + - + - + - + | re-compiled when a binding on the RHS of a LIKE operator changes or when any range constraint changes under [SQLITE_ENABLE_STAT2]. <li>Various minor bug fixes and documentation enhancements. } chng {2009-10-30 (3.6.16.1)} { <li>A small patch to version 3.6.16 to fix |
︙ | |||
3017 3018 3019 3020 3021 3022 3023 | 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 | - + - + | [SQLITE_ENABLE_UPDATE_DELETE_LIMIT]. <li>Added the [sqlite3_stmt_status()] interface for performance monitoring.</li> <li>Add the [INDEXED BY] clause.</li> <li>The LOCKING_STYLE extension is now enabled by default on Mac OS X</li> <li>Added the TRUNCATE option to [PRAGMA journal_mode]</li> <li>Performance enhancements to tree balancing logic in the B-Tree layer.</li> <li>Added the |
︙ | |||
3211 3212 3213 3214 3215 3216 3217 | 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 | - + | the ".dump" output of databases with very large BLOBs and strings can be played back to recreate the database.</li> <li>Other small bug fixes and optimizations.</li> } chng {2007-11-27 (3.5.3)} { <li>Move website and documentation files out of the source tree into |
︙ | |||
3308 3309 3310 3311 3312 3313 3314 | 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 | - + | <li>Improvements to the amalgamation generator script so that all symbols are prefixed with either SQLITE_PRIVATE or SQLITE_API. } chng {2007-07-20 (3.4.1)} { <li>Fix a bug in <a href="lang_vacuum.html">VACUUM</a> that can lead to |
︙ | |||
3341 3342 3343 3344 3345 3346 3347 | 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 | - + | } chng {2007-06-18 (3.4.0)} { <li>Fix a bug that can lead to database corruption if an [SQLITE_BUSY] error occurs in the middle of an explicit transaction and that transaction is later committed. [Ticket #2409]. See the |
︙ | |||
3518 3519 3520 3521 3522 3523 3524 | 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 | - + | } chng {2007-01-09 (3.3.10)} { <li>Fix bugs in the implementation of the new <a href="c3ref/prepare.html">sqlite3_prepare_v2()</a> API that can lead to segfaults.</li> <li>Fix 1-second round-off errors in the |
︙ | |||
3565 3566 3567 3568 3569 3570 3571 | 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 | - + - + - + | same directory as the original database</li> <li>The prefix on temporary filenames on Windows is changed from "sqlite" to "etilqs".</li> } chng {2006-10-09 (3.3.8)} { <li>Support for full text search using the |
︙ | |||
4217 4218 4219 4220 4221 4222 4223 | 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 | - + | another transaction is already active.</li> } chng {2002-08-13 (2.6.3)} { <li>Add the ability to read both little-endian and big-endian databases. So a database created under SunOS or Mac OS X can be read and written under Linux or Windows and vice versa.</li> |
︙ | |||
5146 5147 5148 5149 5150 5151 5152 | 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 | - + | } hd_resolve "</ol></p>\n" hd_resolve { <p>A [complete list of SQLite releases] in a single page and a [chronology] are both also available. A detailed history of every check-in is available at |
Changes to pages/cintro.in.
︙ | |||
421 422 423 424 425 426 427 | 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 | - - + + | <li> [sqlite3_value_int | sqlite3_value()] </li> </ul></p> <p> All of the built-in SQL functions of SQLite are created using exactly these same interfaces. Refer to the SQLite source code, and in particular the |
︙ |
Changes to pages/cli.in.
︙ | |||
486 487 488 489 490 491 492 | 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 | - + | <tclscript>DisplayCode { sqlite> (((SELECT writefile('icon.jpg',img) FROM images WHERE name='icon';))) }</tclscript> <p>Note that the readfile(X) and writefile(X,Y) functions are extension functions and are not built into the core SQLite library. These routines are available as a [loadable extension] in the |
︙ | |||
804 805 806 807 808 809 810 | 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 | - + | pathname of the extension. <p>SQLite computes the entry point for the extension based on the extension filename. To override this choice, simply add the name of the extension as a second argument to the ".load" command. <p>Source code for several useful extensions can be found in the |
︙ | |||
1116 1117 1118 1119 1120 1121 1122 | 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 | - + | statistics can be expensive for large database tables. If the operation is too slow, try passing a smaller value for the --sample option. </table> <p>Th functionality described in this section may be integrated into other applications or tools using the |
︙ |
Changes to pages/compile.in.
︙ | |||
1075 1076 1077 1078 1079 1080 1081 | 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 | - + | 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 for performance analysis. In order for the SQLITE_ENABLE_SQLLOG option to be useful, some extra code is required. The |
︙ | |||
1861 1862 1863 1864 1865 1866 1867 | 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 | - + | A single function declaration should contain no more than one of the following: [SQLITE_APICALL], [SQLITE_CALLBACK], [SQLITE_CDECL], or [SQLITE_SYSCALL]. } COMPILE_OPTION {SQLITE_TCLAPI} { This macro specifies the calling convention used by the |
︙ |
Changes to pages/dev.in.
1 2 3 4 | 1 2 3 4 5 6 7 8 9 | - - - - + + + + | <title>SQLite Developer Links</title> <h1 align="center">Developer Resources</h1> <ul> |
Changes to pages/download.in.
︙ | |||
107 108 109 110 111 112 113 | 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 | - + - + - + - + - + | [https://www.sqlite.org/draft/releaselog/current.html|change log] for more information. } Product {snapshot/sqlite-amalgamation-DATE.zip} { The [amalgamation]: complete source code a single "sqlite3.c" file. } # The [amalgamation] as of VERSION. |
︙ | |||
174 175 176 177 178 179 180 | 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 | - + - + | Product {YEAR/sqlite-amalgamation32k-VVV.zip} { C source code as the [split amalgamation], version VERSION. } Product {YEAR/sqlite-autoconf-VVV.tar.gz} { C source code as an [amalgamation]. Also includes a "configure" script |
︙ | |||
347 348 349 350 351 352 353 | 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 | - + - + | 2013. } if {$nDownload>$start} { hd_puts {<tr><td colspan="4"><b>Precompiled Binaries for .NET</b></td></tr>} hd_puts "<tr><td width=\"10\"></td>" hd_puts "<td valign=\"top\" align=\"right\">" |
︙ | |||
408 409 410 411 412 413 414 | 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 | - + - + - + | <a name="fossil"></a> <tcl>hd_fragment srctree {SQLite source code repositories} {code repositories}</tcl> <h3>Source Code Repositories</h3> <p> The SQLite source code is maintained in three geographically-dispersed self-synchronizing |
︙ |
Changes to pages/famous.in.
︙ | |||
137 138 139 140 141 142 143 | 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 | - + | } famous_user skype http://www.skype.com/ skype.gif { There are [http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html | multiple] [http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27332.html|sightings] of SQLite in the Skype client for Mac OS X and Windows. } |
︙ |
Changes to pages/faq.in.
︙ | |||
575 576 577 578 579 580 581 | 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 | - + | <tt>column1=column1</tt> which is obviously always true. } faq { How are the syntax diagrams (a.k.a. "railroad" diagrams) for SQLite generated? } { |
︙ |
Changes to pages/fileformat2.in.
︙ | |||
361 362 363 364 365 366 367 | 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 | - + | can be set by the [PRAGMA application_id] command in order to identify the database as belonging to or associated with a particular application. The application ID is intended for database files used as an [application file-format]. The application ID can be used by utilities such as [http://www.darwinsys.com/file/ | file(1)] to determine the specific file type rather than just reporting "SQLite3 Database". A list of assigned application IDs can be seen by consulting the |
︙ |
Changes to pages/fts3.in.
︙ | |||
2910 2911 2912 2913 2914 2915 2916 | 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 | - + | of references etc.). These values can be stored by the application in a separate table that can be joined against the documents table in the sub-query so that the rank function may access them. </ol> <p> This version of the query is very similar to that used by the |
︙ |
Changes to pages/fts5.in.
︙ | |||
1966 1967 1968 1969 1970 1971 1972 | 1966 1967 1968 1969 1970 1971 1972 | - - - - | FTS5 table. This shadow table is not present for [FTS5 contentless tables | contentless] or [FTS5 external content tables|external content] FTS5 tables. <tr><td><name>_docsize<td> Contains the size of each column of each row in the virtual table in tokens. This shadow table is not present if the [FTS5 columnsize option|"columnsize" option] is set to 0. </table> |
Changes to pages/getthecode.in.
︙ | |||
22 23 24 25 26 27 28 | 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 | - + | Even if the specific version desired is not listed on the download page, the naming conventions are fairly clear and so programmers can often guess the name of an historical release and download it that way. <h1>Obtaining Code Directly From the Version Control System</h1> <p>For any historical version of SQLite, the source tree can be obtained |
︙ | |||
46 47 48 49 50 51 52 | 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 | - + - + - + - + | [https://www.sqlite.org/cgi/docsrc] (Dallas)<br> [https://www2.sqlite.org/cgi/docsrc] (Newark)<br> [https://www3.sqlite.org/cgi/docsrc] (San Francisco)<br> </blockquote> <p>To download a specific historical version, first locate the specific version desired by visiting the timeline page on one of these servers |
︙ | |||
110 111 112 113 114 115 116 | 110 111 112 113 114 115 116 117 118 | - + | </codeblock> <p>Where VERSION can be a branch name (like "trunk" or "session") to get the latest check-in on a specific branch, or VERSION can be a SHA1 hash or a prefix of a SHA1 hash for a specific check-in, or VERSION can be a tag such as "version-3.8.8". Every time you run "fossil update" it will automatically reach out to the original repository at |
Changes to pages/howtocompile.in.
︙ | |||
143 144 145 146 147 148 149 | 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 | - - - + + + | <h1>Compiling The TCL Interface</h1> <p>The TCL interface for SQLite is a small module that is added into the regular amalgamation. The result is a new amalgamated source file called "<b>tclsqlite3.c</b>". This single source file is all that is needed to generate a shared library that can be loaded into a standard |
︙ | |||
217 218 219 220 221 222 223 | 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 | - + | </ul> <p>To build a custom amalgamation, first download the original individual source files onto a unix or unix-like development platform. Be sure to get the original source files not the "preprocessed source files". One can obtain the complete set of original source files either from the [download page] or directly |
︙ | |||
250 251 252 253 254 255 256 | 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 | - + | <tcl>hd_fragment {dll} {building a DLL}</tcl> <h1>Building A Windows DLL</h1> <p>To build a DLL of SQLite for use in Windows, first acquire the appropriate amalgamated source code files, sqlite3.c and sqlite3.h. These can either |
︙ |
Changes to pages/howtocorrupt.in.
︙ | |||
32 33 34 35 36 37 38 | 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 | - + | old file descriptor, not realizing that the original file had been closed already. But because the file descriptor had been reopened by SQLite, the information that was intended to go into the original file ended up overwriting parts of the SQLite database, leading to corruption of the database.</p> <p>One example of this occurred circa 2013-08-30 on the canonical repository |
︙ | |||
408 409 410 411 412 413 414 | 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 | - + | <tcl>hd_fragment fscorruption {filesystem corruption}</tcl> <h2> Filesystem Corruption</h2> <p>Since SQLite databases are ordinary disk files, any malfunction in the filesystem can corrupt the database. Filesystems in modern operating systems are very reliable, but errors do still occur. For example, on 2013-10-01 the SQLite database that holds the |
︙ |
Changes to pages/lang.in.
︙ | |||
1980 1981 1982 1983 1984 1985 1986 | 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 | - + | </tr> <tr> <td align="right" valign="top"><b>$</b><i>AAAA</i></td><td width="20"></td> <td>^A dollar-sign followed by an identifier name also holds a spot for a named parameter with the name $AAAA. ^(The identifier name in this case can include one or more occurrences of "::" and a suffix enclosed in "(...)" containing any text at all.)^ This syntax is the form of a variable name in the |
︙ | |||
3888 3889 3890 3891 3892 3893 3894 | 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 | - + - + | child checkin is no less than the mtime of all its parents. But unlike the earlier examples, this graph might have multiple paths of differing lengths between any two checkins. <p>We want to know the twenty most recent ancestors in time (out of the thousands and thousands of ancestors in the whole DAG) for checkin "@BASELINE". (A query similar to this is used |
︙ |
Changes to pages/lockingv3.in.
︙ | |||
57 58 59 60 61 62 63 | 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 | - + - + - + | of SQLite version 3. </p> <tcl>HEADING 1 {Overview} overview</tcl> <p> Locking and concurrency control are handled by the |
︙ |
Changes to pages/news.in.
︙ | |||
10 11 12 13 14 15 16 | 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | - + | {<a href="releaselog/\2_\3_\4_\5.html">\0</a>} title]} { regsub -all {(Version) (\d+)\.(\d+)\.(\d+)} $title \ {<a href="releaselog/\2_\3_\4.html">\0</a>} title } hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt regsub -all {[Tt]icket #(\d+)} $txt \ |
︙ |
Changes to pages/oldnews.in.
︙ | |||
266 267 268 269 270 271 272 | 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 | - + - + | <p>This release contains the usual assortment of obscure bug fixes. One bug, however, deserves special attention. A problem appeared in the [CREATE INDEX] command beginning with [version 3.8.2] (2013-12-06) that allowed, under some circumstances, a UNIQUE index to be created on a column that was not unique. Once the index was created, no new non-unique entries could be inserted, but preexisting non-unique entries would remain. See ticket |
︙ | |||
312 313 314 315 316 317 318 | 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 | - + - + - + | the change log for details. } newsitem {2014-04-03} {Release 3.8.4.3} { <p>The optimizations added in [version 3.8.4] caused some queries that involve subqueries in the FROM clause, DISTINCT, and ORDER BY clauses, to give an incorrect result. See |
︙ | |||
379 380 381 382 383 384 385 | 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 | - + | </blockquote> Where all of expr1 through exprN are suitable for use by indexes, then during query planning SQLite might mistakenly converted the "column IS NOT NULL" term into "column>NULL". But the latter term is never true, and so the query would return no rows. <p>The trouble ticket for this bug is |
︙ | |||
439 440 441 442 443 444 445 | 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 | - + | CPU load. } newsitem {2013-10-17} {Release 3.8.1} { <p>SQLite [version 3.8.1] is a regularly scheduled maintenance release. Upgrading from the previous release is optional, though you should upgrade if you are using [partial indices] as there was a |
︙ | |||
527 528 529 530 531 532 533 | 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 | - + | all users are encouraged to upgrade when possible. } newsitem {2013-04-12} {Release 3.7.16.2} { SQLite [version 3.7.16.2] fixes a long-standing flaw in the Windows OS interface that can result in database corruption under a rare race condition. |
︙ | |||
552 553 554 555 556 557 558 | 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 | - + - + | that were present in the previous releases. The primary motivation for version 3.7.16.1 is to fix a bug in the query optimizer that was introduced as part of [version 3.7.15]. The query optimizer was being a little overzealous in optimizing out some ORDER BY clauses, which resulted in sorting being omitted on occasions where sorting is required to get the correct answer. See |
︙ | |||
705 706 707 708 709 710 711 | 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 | - + - + | The next release of SQLite is scheduled to occur after the usual 2 or 3 month interval. } newsitem {2012-05-22} {Patch Release 3.7.12.1} { SQLite [version 3.7.12.1] is a patch release for [version 3.7.12] that |
︙ | |||
778 779 780 781 782 783 784 | 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 | - + | depend on the database page size. Now, if you give [PRAGMA cache_size] a negative value -N, it will allocate roughly N [http://en.wikipedia.org/wiki/Kibibyte | kibibytes] of memory to cache, divided up according to page size. This enhancement allows programs to more easily control their memory usage. There have been several obscure bug fixes. One noteworthy bug, |
︙ | |||
849 850 851 852 853 854 855 | 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 | - + | the SQLite team for mission critical functions and has performed flawlessly. And, of course, it passes our rigorous [testing] procedures with no problems detected. Version 3.7.8 is recommended for all new development. } newsitem {2011-06-28} {Version 3.7.7.1} { SQLite [version 3.7.7.1] adds a one-line bug fix to 3.7.7 to fix |
︙ | |||
899 900 901 902 903 904 905 | 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 | - + | release. But the core SQLite code has changed little and the previous release has not given any problems, so we expect this to be a very stable release. } newsitem {2011-05-19} {Version 3.7.6.3} { SQLite [version 3.7.6.3] is a patch release that fixes a |
︙ | |||
972 973 974 975 976 977 978 | 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 | - + | release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading releases prior to 3.7.5 is recommended. } newsitem {2011-02-01} {Version 3.7.5} { SQLite [version 3.7.5] is a regularly scheduled bi-monthly maintenance release of SQLite. Due to the discovery and fix of |
︙ | |||
1033 1034 1035 1036 1037 1038 1039 | 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 | - + | <li> WinXP and Win7 <li> Android 2.2 <li> OpenBSD 4.7 </ul> The previous release of SQLite ([version 3.7.3]) has proven to be very robust. The only serious issue discovered was |
︙ | |||
1069 1070 1071 1072 1073 1074 1075 | 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 | - + | newsitem {2010-August-24} {Version 3.7.2} { SQLite [version 3.7.2] fixes a long-standing bug that can cause the database [free-page list] to go corrupt if [incremental_vacuum] is used multiple times to partially reduce the size of a database file that contains many hundreds of unused database pages. The original bug reports together with links to the patch that fixes it can be seen |
︙ | |||
1160 1161 1162 1163 1164 1165 1166 | 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 | - + - + | an anachronism. } newsitem {2010-01-06} {Version 3.6.22} { SQLite [version 3.6.22] is a bug-fix release. Two bugs have been fixed that might cause incorrect query results. <ul> |
︙ | |||
1214 1215 1216 1217 1218 1219 1220 | 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 | - + | side to be an arbitrary expression. IS and IS NOT work the same as == (equals) and != (not equals) except that with IS and IS NOT the NULL values compare equal to one another. } newsitem {2009-09-11} {Version 3.6.18} { Beginning with this release, the SQLite source code is tracked and |
︙ | |||
1292 1293 1294 1295 1296 1297 1298 | 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 | - + - + | SQLite [version 3.6.15] is a general maintenance release containing performance and robustness enhancements and fixes for various obscure bugs. } newsitem {2009-05-25} {Version 3.6.14.2} { SQLite [version 3.6.14.2] fixes an obscure bug in the code generator |
︙ | |||
1542 1543 1544 1545 1546 1547 1548 | 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 | - + | allocation subsystem in future releases. } newsitem {2007-10-04} {Version 3.5.1} { Fix a long-standing bug that might cause database corruption if a disk-full error occurs in the middle of a transaction and that transaction is not rolled back. |
︙ | |||
1566 1567 1568 1569 1570 1571 1572 | 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 | - - + + - + - + - + | freeze the new design. } newsitem {2007-08-13} {Version 3.4.2} { While stress-testing the <a href="c3ref/soft_heap_limit.html">soft_heap_limit</a> feature, a bug that could lead to |
︙ | |||
1633 1634 1635 1636 1637 1638 1639 | 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 | - + | newsitem {2007-04-09} {Version 3.3.15} { An annoying bug introduced in 3.3.14 has been fixed. There are also many enhancements to the test suite. } newsitem {2007-04-02} {Version 3.3.14} { This version focuses on performance improvements. If you recompile |
︙ | |||
1670 1671 1672 1673 1674 1675 1676 | 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 | - + - + - + | Version 3.3.10 fixes several bugs that were introduced by the previous release. Upgrading is recommended. } newsitem {2007-01-04} {Version 3.3.9} { Version 3.3.9 fixes bugs that can lead to database corruption under obscure and difficult to reproduce circumstances. See |
︙ | |||
1747 1748 1749 1750 1751 1752 1753 | 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 | - + | the library is running much faster again. Database connections can now be moved between threads as long as the connection holds no locks at the time it is moved. Thus the common paradigm of maintaining a pool of database connections and handing them off to transient worker threads is now supported. Please help test this new feature. |
︙ | |||
1843 1844 1845 1846 1847 1848 1849 | 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 | - + - + | open-source software. Thanks, AOL! Version 3.2.0 also fixes an obscure but serious bug that was discovered just prior to release. If you have a multi-statement transaction and within that transaction an UPDATE or INSERT statement fails due to a constraint, then you try to rollback the whole transaction, the rollback might not work correctly. See |
︙ | |||
1878 1879 1880 1881 1882 1883 1884 | 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 | - + - + - + - + - + - + - + | newsitem {2005-02-15} {Versions 2.8.16 and 3.1.2 Released} { A critical bug in the VACUUM command that can lead to database corruption has been fixed in both the 2.x branch and the main 3.x line. This bug has existed in all prior versions of SQLite. Even though it is unlikely you will ever encounter this bug, it is suggested that all users upgrade. See |
︙ |
Changes to pages/opcode.in.
︙ | |||
134 135 136 137 138 139 140 | 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 | - + | <p> This article also uses the terms "bytecode program" and "prepared statement" interchangeably, as they are mostly the same thing. <h2>VDBE Source Code</h2> <p>The source code to the bytecode engine is in the |
︙ | |||
416 417 418 419 420 421 422 | 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 | - + | All currently defined opcodes are described in the table below. This table was generated automatically by scanning the source code from the file <tcl> if {$uuid==""} { hd_puts "<b>vdbe.c</b>.\n" } else { |
︙ |
Changes to pages/pragma.in.
︙ | |||
243 244 245 246 247 248 249 | 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 | - + | unsigned big-endian "Application ID" integer located at offset 68 into the [database header]. Applications that use SQLite as their [application file-format] should set the Application ID integer to a unique integer so that utilities such as [http://www.darwinsys.com/file/ | file(1)] can determine the specific file type rather than just reporting "SQLite3 Database". A list of assigned application IDs can be seen by consulting the |
︙ |
Changes to pages/privatebranch.in.
︙ | |||
37 38 39 40 41 42 43 | 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 | - + - + | circumstances of each individual project.</p> <img src="images/private_branch.gif" align="right"> <h1> The Basic Idea</h1> <p>We propose to use the |
︙ | |||
100 101 102 103 104 105 106 | 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 | - + - + - + | <p>We emphasize again that these steps are not intended to be the only acceptable method for maintaining private branch. This approach is one of many. Use this document as a baseline for preparing project-specific procedures. Do not be afraid to experiment.</p> <h2> Obtain The Software</h2> |
︙ | |||
345 346 347 348 349 350 351 | 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 | - + - + | Additional private changes can be made on the private branch in between releases if desired.</p> <h1> Variations</h1> <p>Since this document was first written, the canonical SQLite source code has been moved from the venerable CVS system into a Fossil repository at |
︙ |
Changes to pages/queryplanner-ng.in.
︙ | |||
390 391 392 393 394 395 396 | 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 | - + - + | <p>Not all applications meet these conditions. Fortunately, the NGQP will still usually find good query plans, even without these conditions. However, cases do arise (rarely) where performance regressions can occur.</p> <tcl>hd_fragment fossilcasestudy {The Fossil NGQP Upgrade Case Study}</tcl> <h2> Case Study: Upgrading Fossil to the NGQP</h2> |
︙ |
Changes to pages/quickstart.in.
︙ | |||
23 24 25 26 27 28 29 | 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 | - + | <li><p>Additional documentation is available [CLI | here].</li> </ul> <h2>Write Programs That Use SQLite</h2> <ul> <li><p>Below is a simple |
︙ |
Changes to pages/spellfix1.in.
︙ | |||
10 11 12 13 14 15 16 | 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | - + | can be used to suggest corrections to misspelled words. Or, it could be used with [FTS4] to do full-text search using potentially misspelled words. <p>The implementation for the spellfix1 virtual table is held in the SQLite source tree in the miscellaneous extensions folder and in particular in the file |
︙ |
Changes to pages/tclsqlite.in.
1 2 3 4 5 6 7 8 9 10 11 12 13 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | - - + + | <title>The Tcl interface to the SQLite library</title> <tcl> hd_keywords {Tcl extension} {TCL Interface} proc METHOD {name text} { hd_fragment $name [list $name method] [list TCL interface $name method] hd_puts "<h3>The \"$name\" method</h3>\n" hd_resolve $text } </tcl> <h1 align=center>The Tcl interface to the SQLite library</h1> <p>The SQLite library is designed to be very easy to use from |
︙ |
Changes to pages/testing.in.
︙ | |||
152 153 154 155 156 157 158 | 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 | - + | <li><p> <tcl>hd_fragment tcl {TCL test suite}</tcl> The <b>TCL Tests</b> are the oldest set of tests for SQLite. They are contained in the same source tree as the SQLite core and like the SQLite core are in the public domain. The TCL tests are the primary tests used during development. The TCL tests are written using the |
︙ | |||
183 184 185 186 187 188 189 | 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 | - + | instances. The cases that provide 100% branch test coverage constitute a subset of the total TH3 test suite. A soak test prior to release does hundreds of millions of tests. Additional information on TH3 is [TH3 | available separately].</p></li> <li><p> <tcl>hd_fragment slt {SLT} {SQL Logic Tests}</tcl> |
︙ | |||
962 963 964 965 966 967 968 | 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 | - + | <tcl>hd_fragment cklist {release testing checklists} {checklist}</tcl> <h1>Checklists</h1> <p>The SQLite developers use an on-line checklist to coordinate testing activity and to verify that all tests pass prior each SQLite release. |
︙ |
Changes to pages/th3.in.
︙ | |||
49 50 51 52 53 54 55 | 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 | - + | to remedy this problem was the "TH1" (Test Harness #1) scripting language - a reimplementation of parts of the TCL language in a more portable form that would compile and run on SymbianOS, and that was sufficient to run the SQLite tests. TH1 did not survive as a standard testing tool for SQLite, but it did find continued service as a scripting language used to customize the |
︙ |
Changes to pages/undoredo.in.
︙ | |||
82 83 84 85 86 87 88 | 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 | - + | <p> Triggers such as the above could be entered manually, but that is tedious. An important feature of the technique demonstrated below is that the triggers are generated automatically. <p> The implementation language for the example code is |
︙ |
Changes to pages/version3.in.
︙ | |||
95 96 97 98 99 100 101 | 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 | - + | These changes taken together result in database files that are typically 25% to 35% smaller than the equivalent files in SQLite version 2.8. </p> <p> Details of the low-level B-tree format used in SQLite version 3.0 can be found in header comments to the |
︙ |
Changes to pages/vfs.in.
︙ | |||
92 93 94 95 96 97 98 | 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 | - + | VXWorks only. </ol> <p> The various unix VFSes differ only in the way they handle file locking - they share most of their implementation in common with one another and are all located in the same SQLite source file: |
︙ | |||
186 187 188 189 190 191 192 | 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 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 | - + - + - + - + - + - + - + - + | just be a thin wrapper around another VFS that does the real work. We call a wrapper VFS a "shim". </p> <p> A simple example of a shim is the "vfstrace" VFS. This is a VFS (implemented in the |
︙ |
Changes to pages/vtab.in.
︙ | |||
478 479 480 481 482 483 484 | 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 | - - + + | <p>A [virtual table] that contains [hidden columns] can be used like a table-valued function in the FROM clause of a [SELECT] statement. The arguments to the table-valued function become constraints on the HIDDEN columns of the virtual table. <p>For example, the "generate_series" extension (located in the |
︙ |
Changes to pages/withoutrowid.in.
︙ | |||
238 239 240 241 242 243 244 | 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 | - + | tables are implemented using ordinary B-Trees with content stored on both leaves and intermediate nodes. Storing content in intermediate nodes mean that each intermediate node entry takes up more space on the page and thus reduces the fan-out, increasing the search cost. <p>The "sqlite3_analyzer.exe" utility program, available as source code in the SQLite source tree or as a precompiled binary on the |
︙ |