Documentation Source Text

Check-in [5bdcbe6918]
Login

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

Overview
Comment:Fix typos.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:5bdcbe69181174d9d63076fdc8e62ab377a6f991c9c6e34c93b98c86f2a1bf5a
User & Date: drh 2019-04-16 17:15:28
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
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/changes.in.

    77     77        the [sqlite3_db_config]([SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER])
    78     78        setting, or unless the first argument to fts3_tokenizer() is a [bound parameter].
    79     79   <li> The two-argument version of [fts3_tokenizer()] accepts a pointer to the
    80     80        tokenizer method object even without
    81     81        the [sqlite3_db_config]([SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER]) setting
    82     82        if the second argument is a [bound parameter]
    83     83   </ol>     
    84         -<li> Improved robustnessness against corrupt database files.
           84  +<li> Improved robustness against corrupt database files.
    85     85   <li> Miscellaneous performance enhancements
    86     86   <li> Established a Git mirror of the offical SQLite source tree. 
    87     87        The canonical sources for SQLite are maintained using the
    88     88        [https://fossil-scm.org/|Fossil DVCS] at [https://sqlite.org/src].
    89     89        The Git mirror can be seen at [https://github.com/sqlite/sqlite].
    90     90   <p><b>Hashes:</b>
    91     91   <li>SQLITE_SOURCE_ID: <i>Pending</i>

Changes to pages/cli.in.

  1059   1059   <codeblock>
  1060   1060   CREATE TEMP TABLE sqlite_parameters(
  1061   1061     key TEXT PRIMARY KEY,
  1062   1062     value ANY
  1063   1063   ) WITHOUT ROWID;
  1064   1064   </codeblock>
  1065   1065   
  1066         -<p>And if there is a entry in that table where the key column exactly matches
         1066  +<p>And if there is an entry in that table where the key column exactly matches
  1067   1067   the name of parameter (including the initial "?", "$", ":", or "@" character)
  1068   1068   then the parameter is assigned the value of the value column.  If no entry exists,
  1069   1069   the parameter defaults to NULL.
  1070   1070   
  1071   1071   <p>The ".parameter" command exists to simplify managing this table.  The
  1072   1072   ".parameter init" command (often abbreviated as just ".param init") creates
  1073   1073   the temp.sqlite_parameters table if it does not already exist.  The ".param list"

Changes to pages/debugging.in.

   107    107   <li>
   108    108   <p><b>Using the ".breakpoint" shell command</b>
   109    109   
   110    110   <p>The ".breakpoint" command in the CLI does nothing but invoke the
   111    111   procedure named "test_breakpoint()", which is a no-op.
   112    112   
   113    113   <p>If you have a script and you want to start debugging at some point
   114         -half-way through that script, simply set a breakpoing in gdb (or whatever
          114  +half-way through that script, simply set a breakpoint in gdb (or whatever
   115    115   debugger you are using) on the test_breakpoint() function, and add a
   116    116   ".breakpoint" command where you want to stop.  When you reach that first
   117    117   breakpoint, set whatever additional breakpoints are variable traces you
   118    118   need.
   119    119   
   120    120   <li>
   121    121   <p><b>Disable the [lookaside memory allocator]</b>

Changes to pages/security.in.

   111    111   Enable the [PRAGMA cell_size_check=ON] setting.
   112    112   
   113    113   <li><p>
   114    114   Do not enable memory-mapped I/O.
   115    115   In other words, make sure that [PRAGMA mmap_size=0].
   116    116   
   117    117   <li><p>
   118         -A malicously crafted database might be able to inject SQL by defining new
          118  +A maliciously crafted database might be able to inject SQL by defining new
   119    119   [CREATE TRIGGER|triggers] or [CREATE VIEW|views] in the schema that the
   120    120   application does not anticipate.
   121    121   Therefore, applications that read untrusted databases might want to 
   122    122   scan the [sqlite_master] table to look for unexpected triggers and/or views
   123    123   and might also want to deploy the SQL defense techniques described in
   124    124   the previous section.
   125    125   </ol>