Documentation Source Text

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

Changes to pages/changes.in.

    26     26        the [SQLITE_ENABLE_DESERIALIZE] compile-time option is used.
    27     27   <li> Recognize TRUE and FALSE as constants.  (For compatibility, if there
    28     28        exist columns named "true" or "false", then the identifiers refer to the
    29     29        columns rather than Boolean constants.)
    30     30   <li> Support operators IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE.
    31     31   <li> Added the [SQLITE_DBSTATUS_CACHE_SPILL] option to [sqlite3_db_status()] for
    32     32        reporting the number of cache spills that have occurred.
    33         -<li> The "alternate-form-2" flag ("!") on the [built-in printf] implemention
           33  +<li> The "alternate-form-2" flag ("!") on the [built-in printf] implementation
    34     34        now causes string substitutions to measure the width and precision in
    35     35        characters instead of bytes.
    36     36   <li> If the [xColumn] method in a [virtual table] implementation returns
    37     37        an error message using [sqlite3_result_error()] then give that error
    38     38        message preference over internally-generated messages.
    39     39   <li> Added the -A command-line option to the [CLI] to make it easier to manage
    40     40        [SQLite Archive files].

Changes to pages/cli.in.

  1003   1003   
  1004   1004   <h2> SQL Used To Implement SQLite Archive Operations </h2>
  1005   1005   
  1006   1006   <p>The various SQLite Archive Archive commands are implemented using SQL statements.
  1007   1007   Application developers can easily add SQLite Archive Archive reading and writing
  1008   1008   support to their own projects by running the appropriate SQL.
  1009   1009   
  1010         -<p>To see what SQL statements are used to implement an SQLine Archive
         1010  +<p>To see what SQL statements are used to implement an SQLite Archive
  1011   1011   operation, add the --dryrun or -n option.  This causes the SQL to be
  1012   1012   displayed but inhibits the execution of the SQL.
  1013   1013   
  1014   1014   <p>The SQL statements used to implement SQLite Archive operations make use of
  1015   1015   various [loadable extensions].  These extensions are all available in
  1016   1016   the [https://sqlite.org/src|SQLite source tree] in the
  1017   1017   [https://sqlite.org/src/file/ext/misc|ext/misc/ subfolder].

Changes to pages/copyright.in.

    65     65   sources on the internet.
    66     66   
    67     67   <p>
    68     68   Many people associated "open-source" software with software that has
    69     69   grown organically through contributions from countless individuals.
    70     70   And, indeed, there is some open-source software that works that way.
    71     71   But not SQLite.  SQLite uses the the
    72         -[https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar|cathedral development philosopy]
           72  +[https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar|cathedral development philosophy]
    73     73   not the bazaar approach.  All of the SQLite code has been written
    74     74   by people who are well known to each other.
    75     75   
    76     76   <tcl>hd_fragment warrantyoftitle {Warranty of Title}</tcl>
    77     77   
    78     78   <div class="rightsidebar">
    79     79   <form method="GET" action="https://www.hwaci.com/cgi-bin/license-step1">

Changes to pages/lang.in.

  2384   2384   to be false.)^ ^(Values 1, 1.0, 0.1, -0.1 and '1english' are considered to 
  2385   2385   be true.)^
  2386   2386   
  2387   2387   <p>Beginning with SQLite 3.23.0 ([dateof:3.23.0]), SQLite recognizes the
  2388   2388   identifiers "TRUE" and "FALSE" as boolean literals, if and only if those
  2389   2389   identifiers are not already used for some other meaning.  If there already
  2390   2390   exists columns or tables or other objects named TRUE or FALSE, then for
  2391         -the sake of backwards compatibility, the TRUE and FALSE indentifiers refer
         2391  +the sake of backwards compatibility, the TRUE and FALSE identifiers refer
  2392   2392   to those other objects, not to the boolean values.
  2393   2393   
  2394         -<p>The boolean identifers TRUE and FALSE are usually just aliases for
         2394  +<p>The boolean identifiers TRUE and FALSE are usually just aliases for
  2395   2395   the integer values 1 and 0, respectively.  However, if TRUE or FALSE
  2396   2396   occur on the right-hand side of an IS operator, then they form new
  2397   2397   unary postfix operators "IS TRUE" and "IS FALSE" which test the boolean
  2398   2398   value of the operand on the left.
  2399   2399   
  2400   2400   <h3>Functions</h3>
  2401   2401   <p>SQLite supports many [corefunc|simple] and [aggfunc|aggregate]

Changes to pages/tclsqlite.in.

   866    866   The first argument is an integer which is the value of the pointer
   867    867   to the underlying [sqlite3_stmt] object.  This integer can be used
   868    868   to correlate SQL statement text with the result of a <b>profile</b>
   869    869   or <b>row</b> callback. The second argument is the
   870    870   unexpanded text of the SQL statement being run.  By "unexpanded", we
   871    871   mean that variable substitutions in the text are not expanded into the
   872    872   variable values.  This is different from the behavior of the "trace"
   873         -method which does expand variable substitions.
          873  +method which does expand variable substitutions.
   874    874   
   875    875   <p>Traces for <b>profile</b> invoke the callback with two arguments
   876    876   as each SQL statement finishes.  The first argument is an integer which
   877    877   is the value of the underlying [sqlite3_stmt] object.  The second
   878    878   argument is the approximate run-time for the statement in nanoseconds.
   879    879   The run-time is the best estimate available depending on the capabilities
   880    880   of the platform on which the application is running.

Changes to pages/whyc.in.

   149    149   like Rust or Go in which it is impossible, or is at least difficult, to make
   150    150   common programming errors like memory leaks or array overruns.  So the
   151    151   question often arises as to why SQLite is not coded in a "safe" language.
   152    152   
   153    153   <ol>
   154    154   <li><p>
   155    155   None of the safe programming languages existed for the first 10 years
   156         -of SQLite's existance.  SQLite could be recoded in Go or Rust, but doing
          156  +of SQLite's existence.  SQLite could be recoded in Go or Rust, but doing
   157    157   so would probably introduce far more bugs than would be fixed, and it
   158    158   seems also likely to result in slower code.
   159    159   
   160    160   <li><p>
   161    161   Safe programming languages solve the easy problems: memory leaks,
   162    162   use-after-free errors, array overruns, etc.  Safe languages provide
   163    163   no help beyond ordinary C code in solving the rather more difficult