Documentation Source Text

    }
    hd_close_aux
    hd_enable_main 1
  }
}

chng {2009 March 23 (3.6.12)} {
<li>Added the [sqlite3_unlock_notify()] interface.
<li>Added the [reverse_unordered_selects pragma].
<li>The default page size on windows is automatically adjusted to match the
    capabilities of the underlying filesystem.
<li>Add the new ".genfkey" command in the [CLI] for generating triggers to
    implement foreign key constraints.
<li>Performance improvements for "count(*)" queries.
<li>Reduce the amount of heap memory used, especially by TRIGGERs.
}

chng {2009 Feb 18 (3.6.11)} {
<li>Added the [sqlite3_backup_init | hot-backup interface].
<li>Added new commands ".backup" and ".restore" to the [CLI].
<li>Added new methods <a href="tclsqlite.html#backup">backup</a> and
    <a href="tclsqlite.html#restore">restore</a> to the TCL interface.

<p>The macros in this section do not require values. The following 
compilation switches all have the same effect:<br>
-DSQLITE_OMIT_ALTERTABLE<br>
-DSQLITE_OMIT_ALTERTABLE=1<br>
-DSQLITE_OMIT_ALTERTABLE=0
</p>

<p>If any of these options are defined, then the same set of SQLITE_OMIT_*
options must also be defined when using the 'lemon' tool to generate the
parse.c file and when compiling the 'mkkeywordhash' tool which generates 
the keywordhash.h file.
Because of this, these options may only be used when the library is built
from canonical source, not from the [amalgamation] or from the collection of
pre-packaged C files provided for non-Unix like platforms on the website.
Any SQLITE_OMIT_* options which can be used directly with the [amalgamation] 
are listed below, however, the warnings in the following paragraph should be noted.
</p>

<blockquote>
<i><b>Important Note:</b> The SQLITE_OMIT_* options do not work with the
[amalgamation] or with pre-packaged C code files.  SQLITE_OMIT_* compile-time
options only work correctly when SQLite is built from canonical source files.
</i>
</blockquote>


<p>Special versions of the SQLite amalgamation that do work with a
predetermined set of SQLITE_OMIT_* options can be generated.  To do so,
make a copy of the Makefile.linux-gcc makefile template in the canonical
source code distribution.  Change the name of your copy to simply "Makefile".
Then edit "Makefile" to set up appropriate compile-time options.  Then
type:
<blockquote><tt>make clean; make sqlite3.c</tt></blockquote>
The resulting "sqlite3.c" amalgamation code file (and its associated
header file "sqlite3.h") can then be moved to a non-unix platform
for final compilation using a native compiler.</p>

<p>
The following SQLITE_OMIT_* options are available:
</p>

<p><table>
  <tr>
    <td>
      <ul>
        <li> [SQLITE_OMIT_AUTHORIZATION] </li>
        <li> [SQLITE_OMIT_AUTOINIT] </li>

        <li> [SQLITE_OMIT_XFER_OPT] </li>
      </ul>
    </td>
  </tr>
</table>
</p>


<p>All of the SQLITE_OMIT_* options are unsupported.</p>

<blockquote>
<i><b>Important Note:</b>
The SQLITE_OMIT_* compile-time options are unsupported.
</i></blockquote>

<p>
The SQLITE_OMIT_* compile-time options are usually untested and
are almost certainly untested in combination.
Any or all of these options may be removed from the code in future releases
and without warning.  For any particular release, some of these
options may cause compile-time or run-time failures, particularly
when used in combination with other options.</p>

<tcl>
COMPILE_OPTION {SQLITE_OMIT_ALTERTABLE} {
  When this option is defined, the 

  <p>As of [Version 3.6.12] this feature is incorporated into the CLI.</p>
  
  <p>You can read about other possible solutions for foreign key
  support in the
  <a href="http://www.sqlite.org/cvstrac/wiki?p=ForeignKeyTriggers">SQLite Wiki</a>.</p>
}

faq {
  I get a compiler error if I use the SQLITE_OMIT_... 
  compile-time options when building SQLite.
} {
  The [omitfeatures | SQLITE_OMIT_...] compile-time options only work
  when building from canonically source files.  They do <u>not</u> work
  when you build from the SQLite [amalgamation] or from the pre-processed
  source files.

  It is possible to build a special [amalgamation] that will work with
  a predetermined set of SQLITE_OMIT_... options.  Instructions for doing
  so can be found with the [omitfeatures | SQLITE_OMIT_... documentation].
}

# End of questions and answers.
#############

hd_puts {<h2>Frequently Asked Questions</h2>}
hd_puts {<p>See also <a href="http://www.sqlite.org/cvstrac/wiki?p=SqliteWikiFaq">SqliteWikiFaq</a>.</p>}

.backup ?DB? FILE      Backup DB (default "main") to FILE
.bail ON|OFF           Stop after hitting an error.  Default OFF
.databases             List names and files of attached databases
.dump ?TABLE? ...      Dump the database in an SQL text format
.echo ON|OFF           Turn command echo on or off
.exit                  Exit this program
.explain ON|OFF        Turn output mode suitable for EXPLAIN on or off.
.genfkey ?OPTIONS?     Options are:
                         --no-drop: Do not drop old fkey triggers.
                         --ignore-errors: Ignore tables with fkey errors
                         --exec: Execute generated SQL immediately
                       See file tool/genfkey.README in the source 
                       distribution for further information.
.header(s) ON|OFF      Turn display of headers on or off
.help                  Show this message
.import FILE TABLE     Import data from FILE into TABLE
.indices TABLE         Show names of all indices on TABLE
.iotrace FILE          Enable I/O diagnostic logging to FILE
.load FILE ?ENTRY?     Load an extension library
.mode MODE ?TABLE?     Set output mode where MODE is one of: