Documentation Source Text

Check-in [2a08b85198]
Login

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

Overview
Comment:Typo fixes.
Timelines: family | ancestors | descendants | both | branch-3.19
Files: files | file ages | folders
SHA3-256: 2a08b85198397450c5ad25a63e8280b6ba47217c51afc55402b175dd5378ac6e
User & Date: drh 2017-07-10 18:11:17
Context
2017-07-10
19:49
Fix a typo in the dbstat.html document. check-in: 4160ca5c08 user: drh tags: branch-3.19
18:11
Typo fixes. check-in: 2a08b85198 user: drh tags: branch-3.19
2017-07-09
18:49
Fix typo in the appfileformat.html document. check-in: 67789bcd04 user: drh tags: branch-3.19
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/copyright.in.

    47     47   
    48     48   <div class="rightsidebar">
    49     49   <form method="GET" action="https://www.hwaci.com/cgi-bin/license-step1">
    50     50   <input type="submit" value="Buy An SQLite License">
    51     51   </form>
    52     52   </div>
    53     53   
    54         -<h2>Obtaining An License To Use SQLite</h2>
           54  +<h2>Obtaining A License To Use SQLite</h2>
    55     55   
    56     56   <p>
    57     57   Even though SQLite is in the public domain and does not require
    58     58   a license, some users want to obtain a license anyway.  Some reasons
    59     59   for obtaining a license include:
    60     60   </p>
    61     61   

Changes to pages/faq.in.

     7      7     incr ::cnt
     8      8   }
     9      9   
    10     10   #############
    11     11   # Enter questions and answers here.
    12     12   
    13     13   faq {
    14         -  How do I create an AUTOINCREMENT field.
           14  +  How do I create an AUTOINCREMENT field?
    15     15   } {
    16     16     <p>Short answer: A column declared [INTEGER PRIMARY KEY] will
    17     17     autoincrement.</p>
    18     18   
    19     19     <p>Longer answer:
    20     20     If you declare a column of a table to be [INTEGER PRIMARY KEY], then
    21     21     whenever you insert a NULL

Changes to pages/privatebranch.in.

   355    355   simply by cloning the official repository:</p>
   356    356   
   357    357   <blockquote><pre>
   358    358   fossil clone http://www.sqlite.org/src private-project.fossil
   359    359   </pre></blockquote>
   360    360   
   361    361   <p>This command both creates the new repository and populates it with
   362         -all the latest SQLite could.  You can the create a private branch as
          362  +all the latest SQLite could.  You can then create a private branch as
   363    363   described in section 3.4.</p>
   364    364   
   365    365   <p>When the private repository is created by cloning, incorporating new
   366    366   public SQLite releases becomes much easier too.  To pull in all of the
   367    367   latest changes from the public SQLite repository, simply move into
   368    368   the open check-out and do:</p>
   369    369   
   370    370   <blockquote><pre>
   371    371   fossil update
   372    372   </pre></blockquote>
   373    373   
   374    374   <p>Then continue to merge the changes in "trunk" with your "private"
   375    375   changes as described in section 3.7.</p>

Changes to pages/rbu.in.

    49     49   The total amount of data written is around three times the size of the
    50     50   final database file. By contrast, an RBU Vacuum requires roughly the size
    51     51   of the final database file in temporary disk space and writes a total of
    52     52   twice that to disk.
    53     53   
    54     54   <p>On the other hand, an RBU Vacuum uses more CPU than a regular SQLite
    55     55   VACUUM - in one test as much as five times as much. For this reason, an RBU
    56         -Vaccum is often significantly slower than an SQLite VACUUM under the same
           56  +Vacuum is often significantly slower than an SQLite VACUUM under the same
    57     57   conditions.
    58     58   
    59     59   <li><b>RBU runs in the background</b>
    60     60   
    61     61   <p>An ongoing RBU operation (either an update or a vacuum) does not
    62     62   interfere with read access to the database file.
    63     63   
................................................................................
   100    100   <li><p>The target database may not contain [indexes on expressions].
   101    101   <li><p>No other writes may occur on the target database while the
   102    102          RBU update is being applied.  A read-lock is held on the target
   103    103          database to prevent this.</p></li>
   104    104   </ul>
   105    105   
   106    106   
   107         -<h2>Preparing An RBU Update File</h2>
          107  +<h2>Preparing an RBU Update File</h2>
   108    108   
   109    109   <p>All changes to be applied by RBU are stored in a separate SQLite database
   110    110   called the "RBU database".  The database that is to be modified is called
   111    111   the "target database".
   112    112   
   113    113   <p>For each table in the target database that will be modified by the update,
   114    114   a corresponding table is created within the RBU database. The RBU database
................................................................................
   233    233   <p>is represented by the data_t1 row created by:
   234    234   
   235    235   <codeblock>
   236    236   INSERT INTO data_t1(a, b, c, rbu_control) VALUES(4, NULL, 'usa', '..x');
   237    237   </codeblock>
   238    238   
   239    239   <p>If RBU is used to update a large BLOB value within a target database, it
   240         -may be be more efficient to store a patch or delta that can be used to modify
          240  +may be more efficient to store a patch or delta that can be used to modify
   241    241   the existing BLOB instead of an entirely new value within the RBU database. 
   242    242   RBU allows deltas to be specified in two ways:
   243    243   
   244    244   <ul>
   245    245     <li> In the "fossil delta" format - the format used for blob deltas by the 
   246    246     <a href=http://fossil-scm.org>Fossil source-code management system</a>, or
   247    247   

Changes to pages/sqldiff.in.

    33     33   <dd><p>Use the schema-defined [PRIMARY KEY] instead of the [rowid] to
    34     34          pair rows in the source and destination database.  (See additional
    35     35          explanation below.)</dd>
    36     36   <dt><b>--schema</b></dt>
    37     37   <dd><p>Show only differences in the schema not the table content</p></dd>
    38     38   <dt><b>--summary</b></dt>
    39     39   <dd><p>Show how many rows have changed on each table, but do not show
    40         -       the actual chagnes</dd>
           40  +       the actual changes</dd>
    41     41   <dt><b>--table TABLE</b></dt>
    42     42   <dd><p>Show only the differences in content for TABLE, not for the
    43     43          entire database</p></dd>
    44     44   <dt><b>--transaction</b></dt>
    45     45   <dd><p>Wrap SQL output in a single large transaction</p></dd>
    46     46   <dt><b>--vtab</b></dt>
    47     47   <dd><p>Add support for handling [FTS3], [FTS5] and [rtree] virtual tables. 
................................................................................
    89     89   [CREATE TRIGGER|TRIGGERs] or [CREATE VIEW|VIEWs].
    90     90   
    91     91   <li><p id=vtab>
    92     92   By default, differences in the schema or content of virtual tables are
    93     93   not reported on. 
    94     94   
    95     95   <p>However, if a [virtual table] implementation creates real tables (sometimes
    96         -refered to as "shadow" tables) within the database to store its data in, then
           96  +referred to as "shadow" tables) within the database to store its data in, then
    97     97   sqldiff.exe does calculate the difference between these. This can have
    98     98   surprising effects if the resulting SQL script is then run on a database that
    99     99   is not <i>exactly</i> the same as the source database. For several of SQLite's
   100    100   bundled virtual tables (FTS3, FTS5, rtree and others), the surprising effects
   101    101   may include corruption of the virtual table content.
   102    102   
   103    103   <p> If the --vtab option is passed to sqldiff.exe, then it ignores all 
   104    104   underlying shadow tables belonging to an FTS3, FTS5 or rtree virtual table
   105    105   and instead includes the virtual table differences directly.
   106    106   
   107    107   </ol>