Documentation Source Text

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

Changes to pages/different.in.

    90     90     Most other SQL database engines require you to dump and restore
    91     91     the database when moving from one platform to another and often
    92     92     when upgrading to a newer version of the software.
    93     93   }
    94     94   
    95     95   feature small {Compact} {
    96     96     When optimized for size, the whole SQLite library with everything enabled
    97         -  is less than 225KiB in size (as measured on an ix86 using the "size"
           97  +  is less than 275KiB in size (as measured on an ix86 using the "size"
    98     98     utility from the GNU compiler suite.)  Unneeded features can be disabled
    99     99     at compile-time to further reduce the size of the library to under
   100         -  170KiB if desired.
          100  +  190KiB if desired.
   101    101     <p>
   102    102     Most other SQL database engines are much larger than this.  IBM boasts
   103    103     that its recently released CloudScape database engine is "only" a 2MiB
   104         -  jar file - 10 times larger than SQLite even after it is compressed!
          104  +  jar file - an order of magnitude larger than SQLite even after it is
          105  +  compressed!
   105    106     Firebird boasts that its client-side library is only 350KiB.  That's
   106    107     50% larger than SQLite and does not even contain the database engine.
   107         -  The Berkeley DB library from Sleepycat is 450KiB and it omits SQL
          108  +  The Berkeley DB library from Oracle is 450KiB and it omits SQL
   108    109     support, providing the programmer with only simple key/value pairs.
   109    110   }
   110    111   
   111    112   feature typing {Manifest typing} {
   112    113     Most SQL database engines use static typing.  A datatype is associated
   113    114     with each column in a table and only values of that particular datatype
   114    115     are allowed to be stored in that column.  SQLite relaxes this restriction

Changes to pages/testing.in.

   248    248   failure.</p>
   249    249   
   250    250   <p>In I/O error tests, after the I/O error simulation failure mechanism
   251    251   is disabled, the database is examined using
   252    252   [PRAGMA integrity_check] to make sure that the I/O error has not
   253    253   introduced database corruption.</p>
   254    254   
   255         -<h3>3.2 Crash Testing</h3>
          255  +<h3>3.3 Crash Testing</h3>
   256    256   
   257    257   <p>Crash testing seeks to demonstrate that an SQLite database will not
   258    258   go corrupt if the application or operating system crashes or if there
   259    259   is a power failure in the middle of a database update.  A separate
   260    260   white-paper titled
   261    261   <a href="atomiccommit.html">Atomic Commit in SQLite</a> describes the
   262    262   defensive measure SQLite takes to prevent database corruption following
................................................................................
   292    292   damage is introduced that is characteristic of the kinds of damage
   293    293   one expects to see following a power loss.  Then the database is opened
   294    294   and checks are made to ensure that it is well-formed and that the
   295    295   transaction either ran to completion or was completely rolled back.
   296    296   The interior of the loop is repeated multiple times for each
   297    297   snapshot with different random damage each time.</p>
   298    298   
   299         -<h3>3.3 Compound failure tests</h3>
          299  +<h3>3.4 Compound failure tests</h3>
   300    300   
   301    301   <p>The test suites for SQLite also explore the result of stacking
   302    302   multiple failures.  For example, tests are run to insure correct behavior
   303    303   when an I/O error or OOM fault occurs while trying to recover from a
   304    304   prior crash.
   305    305   
   306    306   <h2>4.0 Fuzz Testing</h2>