Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix typos. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
5bdcbe69181174d9d63076fdc8e62ab3 |
User & Date: | drh 2019-04-16 17:15:28.711 |
Context
2019-04-16
| ||
19:52 | Version 3.28.0 (check-in: 8084bf3aaf user: drh tags: trunk, release, version-3.28.0) | |
17:15 | Fix typos. (check-in: 5bdcbe6918 user: drh tags: trunk) | |
17:08 | Add a news entry for the 3.28.0 release. (check-in: 4136052d27 user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
77 78 79 80 81 82 83 | the [sqlite3_db_config]([SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]) setting, or unless the first argument to fts3_tokenizer() is a [bound parameter]. <li> The two-argument version of [fts3_tokenizer()] accepts a pointer to the tokenizer method object even without the [sqlite3_db_config]([SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]) setting if the second argument is a [bound parameter] </ol> | | | 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 | the [sqlite3_db_config]([SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]) setting, or unless the first argument to fts3_tokenizer() is a [bound parameter]. <li> The two-argument version of [fts3_tokenizer()] accepts a pointer to the tokenizer method object even without the [sqlite3_db_config]([SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]) setting if the second argument is a [bound parameter] </ol> <li> Improved robustness against corrupt database files. <li> Miscellaneous performance enhancements <li> Established a Git mirror of the offical SQLite source tree. The canonical sources for SQLite are maintained using the [https://fossil-scm.org/|Fossil DVCS] at [https://sqlite.org/src]. The Git mirror can be seen at [https://github.com/sqlite/sqlite]. <p><b>Hashes:</b> <li>SQLITE_SOURCE_ID: <i>Pending</i> |
︙ | ︙ |
Changes to pages/cli.in.
︙ | ︙ | |||
1059 1060 1061 1062 1063 1064 1065 | <codeblock> CREATE TEMP TABLE sqlite_parameters( key TEXT PRIMARY KEY, value ANY ) WITHOUT ROWID; </codeblock> | | | 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 | <codeblock> CREATE TEMP TABLE sqlite_parameters( key TEXT PRIMARY KEY, value ANY ) WITHOUT ROWID; </codeblock> <p>And if there is an entry in that table where the key column exactly matches the name of parameter (including the initial "?", "$", ":", or "@" character) then the parameter is assigned the value of the value column. If no entry exists, the parameter defaults to NULL. <p>The ".parameter" command exists to simplify managing this table. The ".parameter init" command (often abbreviated as just ".param init") creates the temp.sqlite_parameters table if it does not already exist. The ".param list" |
︙ | ︙ |
Changes to pages/debugging.in.
︙ | ︙ | |||
107 108 109 110 111 112 113 | <li> <p><b>Using the ".breakpoint" shell command</b> <p>The ".breakpoint" command in the CLI does nothing but invoke the procedure named "test_breakpoint()", which is a no-op. <p>If you have a script and you want to start debugging at some point | | | 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 | <li> <p><b>Using the ".breakpoint" shell command</b> <p>The ".breakpoint" command in the CLI does nothing but invoke the procedure named "test_breakpoint()", which is a no-op. <p>If you have a script and you want to start debugging at some point half-way through that script, simply set a breakpoint in gdb (or whatever debugger you are using) on the test_breakpoint() function, and add a ".breakpoint" command where you want to stop. When you reach that first breakpoint, set whatever additional breakpoints are variable traces you need. <li> <p><b>Disable the [lookaside memory allocator]</b> |
︙ | ︙ |
Changes to pages/security.in.
︙ | ︙ | |||
111 112 113 114 115 116 117 | Enable the [PRAGMA cell_size_check=ON] setting. <li><p> Do not enable memory-mapped I/O. In other words, make sure that [PRAGMA mmap_size=0]. <li><p> | | | 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 | Enable the [PRAGMA cell_size_check=ON] setting. <li><p> Do not enable memory-mapped I/O. In other words, make sure that [PRAGMA mmap_size=0]. <li><p> A maliciously crafted database might be able to inject SQL by defining new [CREATE TRIGGER|triggers] or [CREATE VIEW|views] in the schema that the application does not anticipate. Therefore, applications that read untrusted databases might want to scan the [sqlite_master] table to look for unexpected triggers and/or views and might also want to deploy the SQL defense techniques described in the previous section. </ol> |
︙ | ︙ |