Differences

This shows you the differences between two versions of the page.

howtos:sqlite_tutorial [2007/01/23 02:08]
texasfett
howtos:sqlite_tutorial [2013/10/25 14:52] (current)
xuesheng Stop the wiki making PostgreSQL into a broken link
Line 1: Line 1:
-====== SQLite Tutorial ====== +====== 'sqlite' Tutorial for POPFile 0.21.0 to 1.0.1 ====== 
-a command-line program to administer SQLite databases+ 
 +**'sqlite'** is a command-line program to administer SQLite 2.x databases as used by POPFile 0.21.0 to 1.0.1. This utility is called **''sqlite.exe''** or **''sqlite''** depending upon the platform. For simplicity this tutorial refers to the utility as **''sqlite''**. 
 + 
 +^ POPFile 1.1.0 (or later) uses the SQLite 3.x format for its database which requires a different command-line program (**''sqlite3.exe''** or **''sqlite3''**). There is a [[http://www.sqlite.org/sqlite.html | tutorial]] showing how to use this SQLite 3.x format utility on the SQLite website.^ 
==== Introduction ==== ==== Introduction ====
-POPFile uses an SQLite database to hold essential information, such as the corpus used to classify the messages it handles. At present POPFile only works with SQLite 2.x libraries, even though SQLite 3.x libraries are available.+POPFile uses an SQLite database to hold essential information, such as the corpus used to classify the messages it handles. POPFile versions 0.21.0 to 1.0.1 only work with SQLite 2.x libraries (none of these versions can work with SQLite 3.x libraries).
-The SQLite library includes a simple command-line utility that allows the user to manually enter and execute SQL commands against an SQLite database. Databases built using SQLite 2.x libraries are not compatible with databases built using the SQLite 3.x libraries. Therefore there are separate command-line utilities: **sqlite** for SQLite 2.x format databases and **sqlite3** for SQLite 3.x format databases.+The SQLite library includes a simple command-line utility that allows the user to manually enter and execute SQL commands against an SQLite database. Databases built using SQLite 2.x libraries are not compatible with databases built using the SQLite 3.x libraries. Therefore there are separate command-line utilities: **''sqlite''** for SQLite 2.x format databases and **''sqlite3''** for SQLite 3.x format databases.
-The SQLite web site only seems to document the **sqlite3** utility which is not compatible with the SQLite databases created by POPFile. The information on this wiki page is based upon an old page (last modified on 2004/05/31 15:06:30) from the SQLite web site which documented the features supported by the **sqlite** command-line utility.+The SQLite web site only seems to document the **''sqlite3''** utility which is not compatible with the SQLite databases created by POPFile 0.21.0 to 1.0.1 (POPFile 1.1.0, or later, uses SQLite 3.x). The information on this wiki page is based upon an old page (last modified on 2004/05/31 15:06:30) from the SQLite web site which documented the features supported by the **''sqlite''** command-line utility.
-The SQLite web site still has some [[http://www.sqlite.org/download.html | download links]] for the old **sqlite** command-line utility (listed under "Historical Binaries And Source Code").+The SQLite web site's [[http://www.sqlite.org/download.html | download]] page no longer has links for the old **''sqlite''** command-line utility (Windows and Linux binary versions used to be listed under "Historical Binaries And Source Code") but the SQLite 2.8 source code is still available. (POPFile's Windows installer includes a SQLite 2.x version of the **''sqlite.exe''** command-line utility.)
==== Getting Started ==== ==== Getting Started ====
-To start the **sqlite** program, just type "sqlite" (without the quotes!) followed by the name of the file that holds the SQLite database. If the file does not exist, a new one is created automatically. The **sqlite** program will then prompt you to enter SQL. Type in SQL statements (terminated by a semicolon), press "Enter" and the SQL will be executed.+To start the **''sqlite''** program, just type ''sqlite'' at the command prompt ((If you want to use ''sqlite'' with an existing SQLite database file it is best to change to the directory containing the database file before you run ''sqlite'')) followed by the name of the file that holds the SQLite database. If the file does not exist, a new one is created automatically (**NOTE**: The program **__will not__** warn that it has created an empty SQLite database). The **''sqlite''** program will then prompt you to enter SQL. Type in SQL statements (terminated by a semicolon), press "Enter" and the SQL will be executed.
-For example, to create a new SQLite database named "ex1" with a single table named "tbl1", you might do this:+For example, to create a new SQLite database named **''ex1''** with a single table named **''tbl1''**, you might do this:
<code> <code>
Line 32: Line 36:
</code> </code>
-You can terminate the sqlite program by typing your systems End-Of-File character (usually a Control-D) or the interrupt character (usually a Control-C).+You can terminate the **''sqlite''** program by typing your system's End-Of-File character (usually a Control-D) or the interrupt character (usually a Control-C).
-Make sure you type a semicolon at the end of each SQL command! The sqlite looks for a semicolon to know when your SQL command is complete. If you omit the semicolon, **sqlite** will give you a continuation prompt and wait for you to enter more text to be added to the current SQL command. This feature allows you to enter SQL commands that span multiple lines. For example:+Make sure you type a semicolon at the end of each SQL command! The **''sqlite''** program looks for a semicolon to know when your SQL command is complete. If you omit the semicolon, **''sqlite''** will give you a continuation prompt and wait for you to enter more text to be added to the current SQL command. This feature allows you to enter SQL commands that span multiple lines. For example:
<code> <code>
Line 44: Line 48:
sqlite> sqlite>
</code> </code>
 +
==== Aside: Querying the SQLITE_MASTER table ==== ==== Aside: Querying the SQLITE_MASTER table ====
-The database schema in an SQLite database is stored in a special table named "sqlite_master". You can execute "SELECT" statements against the special sqlite_master table just like any other table in an SQLite database. For example:+The database schema in an SQLite database is stored in a special table named "''sqlite_master''". You can execute **SELECT** statements against the special "''sqlite_master''" table just like any other table in an SQLite database. For example:
<code> <code>
Line 64: Line 69:
</code> </code>
-But you cannot execute DROP TABLE, UPDATE, INSERT or DELETE against the sqlite_master table. The sqlite_master table is updated automatically as you create or drop tables and indices from the database. You can not make manual changes to the sqlite_master table. +But you cannot execute DROP TABLE, UPDATE, INSERT or DELETE against the "''sqlite_master''" table. The "''sqlite_master''" table is updated automatically as you create or drop tables and indices from the database. You can not make manual changes to the "''sqlite_master''" table.
-The schema for TEMPORARY tables is not stored in the "sqlite_master" table since TEMPORARY tables are not visible to applications other than the application that created the table. The schema for TEMPORARY tables is stored in another special table named "sqlite_temp_master". The "sqlite_temp_master" table is temporary itself. +The schema for TEMPORARY tables is not stored in the "''sqlite_master''" table since TEMPORARY tables are not visible to applications other than the application that created the table. The schema for TEMPORARY tables is stored in another special table named "''sqlite_temp_master''". The "''sqlite_temp_master''" table is temporary itself.
-==== Special commands to sqlite ==== 
-Most of the time, sqlite just reads lines of input and passes them on to the SQLite library for execution. But if an input line begins with a dot ("."), then that line is intercepted and interpreted by the sqlite program itself. These "dot commands" are typically used to change the output format of queries, or to execute certain prepackaged query statements. +==== Special commands to 'sqlite' ====
-For a listing of the available dot commands, you can enter ".help" at any time. For example: +Most of the time, **''sqlite''** just reads lines of input and passes them on to the SQLite library for execution. But if an input line begins with a dot ("."), then that line is intercepted and interpreted by the **''sqlite''** program itself. These "dot commands" are typically used to change the output format of queries, or to execute certain prepackaged query statements.  
 + 
 +For a listing of the available dot commands, you can enter **''.help''** at any time. For example:
<code> <code>
Line 102: Line 108:
sqlite> sqlite>
</code> </code>
 +
==== Changing Output Formats ==== ==== Changing Output Formats ====
-The sqlite program is able to show the results of a query in five different formats: "line", "column", "list", "html", and "insert". You can use the ".mode" dot command to switch between these output formats.+The **''sqlite''** program is able to show the results of a query in five different formats: "line", "column", "list", "html", and "insert". You can use the **''.mode''** dot command to switch between these output formats.
-The default output mode is "list". In list mode, each record of a query result is written on one line of output and each column within that record is separated by a specific separator string. The default separator is a pipe symbol ("|"). List mode is especially useful when you are going to send the output of a query to another program (such as AWK) for additional processing.+The default output mode is **list**. In list mode, each record of a query result is written on one line of output and each column within that record is separated by a specific separator string. The default separator is a pipe symbol ("|"). List mode is especially useful when you are going to send the output of a query to another program (such as AWK) for additional processing.
<code> <code>
Line 118: Line 125:
</code> </code>
-You can use the ".separator" dot command to change the separator for list mode. For example, to change the separator to a comma and a space, you could do this:+You can use the **''.separator''** dot command to change the separator for list mode. For example, to change the separator to a comma and a space, you could do this:
<code> <code>
Line 128: Line 135:
</code> </code>
-In "line" mode, each column in a row of the database is shown on a line by itself. Each line consists of the column name, an equal sign and the column data. Successive records are separated by a blank line. Here is an example of line mode output:+In **line** mode, each column in a row of the database is shown on a line by itself. Each line consists of the column name, an equal sign and the column data. Successive records are separated by a blank line. Here is an example of line mode output:
<code> <code>
Line 141: Line 148:
</code> </code>
-In column mode, each record is shown on a separate line with the data aligned in columns. For example:+In **column** mode, each record is shown on a separate line with the data aligned in columns. For example:
<code> <code>
Line 154: Line 161:
</code> </code>
-By default, each column is at least 10 characters wide. Data that is too wide to fit in a column is truncated. You can adjust the column widths using the ".width" command. Like this:+By default, each column is at least 10 characters wide. Data that is too wide to fit in a column is truncated. You can adjust the column widths using the **''.width''** command. Like this:
<code> <code>
Line 168: Line 175:
</code> </code>
-The ".width" command in the example above sets the width of the first column to 12 and the width of the second column to 6. All other column widths were unaltered. You can gives as many arguments to ".width" as necessary to specify the widths of as many columns as are in your query results.+The **''.width''** command in the example above sets the width of the first column to 12 and the width of the second column to 6. All other column widths were unaltered. You can gives as many arguments to **''.width''** as necessary to specify the widths of as many columns as are in your query results.
If you specify a column a width of 0, then the column width is automatically adjusted to be the maximum of three numbers: 10, the width of the header, and the width of the first row of data. This makes the column width self-adjusting. The default width setting for every column is this auto-adjusting 0 value. If you specify a column a width of 0, then the column width is automatically adjusted to be the maximum of three numbers: 10, the width of the header, and the width of the first row of data. This makes the column width self-adjusting. The default width setting for every column is this auto-adjusting 0 value.
-The column labels that appear on the first two lines of output can be turned on and off using the ".header" dot command. In the examples above, the column labels are on. To turn them off you could do this:+The column labels that appear on the first two lines of output can be turned on and off using the **''.header''** dot command. In the examples above, the column labels are on. To turn them off you could do this:
<code> <code>
Line 182: Line 189:
</code> </code>
-Another useful output mode is "insert". In insert mode, the output is formatted to look like SQL INSERT statements. You can use insert mode to generate text that can later be used to input data into a different database.+Another useful output mode is **insert**. In **insert** mode, the output is formatted to look like SQL INSERT statements. You can use **insert** mode to generate text that can later be used to input data into a different database.
-When specifying insert mode, you have to give an extra argument which is the name of the table to be inserted into. For example:+When specifying **insert** mode, you have to give an extra argument which is the name of the table to be inserted into. For example:
<code> <code>
Line 194: Line 201:
</code> </code>
-The last output mode is "html". In this mode, sqlite writes the results of the query as an XHTML table. The beginning <TABLE> and the ending </TABLE> are not written, but all of the intervening <TR>s, <TH>s, and <TD>s are. For example:+The last output mode is **html**. In this mode, **''sqlite''** writes the results of the query as an XHTML table. The beginning <TABLE> and the ending </TABLE> are not written, but all of the intervening <TR>s, <TH>s, and <TD>s are. For example:
<code> <code>
Line 208: Line 215:
</code> </code>
-The html output mode is envisioned as being useful for CGI.+The **html** output mode is envisioned as being useful for CGI. 
==== Writing results to a file ==== ==== Writing results to a file ====
-By default, sqlite sends query results to standard output. You can change this using the ".output" command. Just put the name of an output file as an argument to the .output command and all subsequent query results will be written to that file. Use ".output stdout" to begin writing to standard output again. For example:+By default, **''sqlite''** sends query results to standard output. You can change this using the **''.output''** command. Just put the name of an output file as an argument to the **''.output''** command and all subsequent query results will be written to that file. Use **''.output stdout''** to begin writing to standard output again. For example:
<code> <code>
Line 226: Line 234:
$ $
</code> </code>
- 
Line 233: Line 240:
==== Querying the database schema ==== ==== Querying the database schema ====
-The sqlite program provides several convenience commands that are useful for looking at the schema of the database. There is nothing that these commands do that cannot be done by some other means. These commands are provided purely as a shortcut.+The **''sqlite''** program provides several convenience commands that are useful for looking at the schema of the database. There is nothing that these commands do that cannot be done by some other means. These commands are provided purely as a shortcut.
-For example, to see a list of the tables in the database, you can enter ".tables".+For example, to see a list of the tables in the database, you can enter **''.tables''**.
<code> <code>
sqlite> .tables sqlite> .tables
-tbl1 +tbl1 tbl2
-tbl2+
sqlite> sqlite>
</code> </code>
-The ".tables" command is the same as setting list mode then executing the following query:+The **''.tables''** command is equvalent to executing the following query:
<code sql> <code sql>
Line 252: Line 258:
</code> </code>
-In fact, if you look at the source code to the sqlite program (found in the source tree in the file src/shell.c) you'll find exactly the above query.+In fact, if you look at the source code to the **''sqlite''** program (found in the source tree in the file src/shell.c) you'll find exactly the above query.
-The ".indices" command works in a similar way to list all of the indices for a particular table. The ".indices" command takes a single argument which is the name of the table for which the indices are desired. Last, but not least, is the ".schema" command. With no arguments, the ".schema" command shows the original CREATE TABLE and CREATE INDEX statements that were used to build the current database. If you give the name of a table to ".schema", it shows the original CREATE statement used to make that table and all if its indices. We have:+The **''.indices''** command works in a similar way to list all of the indices for a particular table. The **''.indices''** command takes a single argument which is the name of the table for which the indices are desired. 
 + 
 +Last, but not least, is the **''.schema''** command. With no arguments, the **''.schema''** command shows the original CREATE TABLE and CREATE INDEX statements that were used to build the current database. If you give the name of a table to **''.schema''**, it shows the original CREATE statement used to make that table and all if its indices. We have:
<code> <code>
Line 273: Line 281:
</code> </code>
-The ".schema" command accomplishes the same thing as setting list mode, then entering the following query:+The **''.schema''** command accomplishes the same thing as setting list mode, then entering the following query:
<code sql> <code sql>
Line 283: Line 291:
</code> </code>
-Or, if you give an argument to ".schema" because you only want the schema for a single table, the query looks like this:+Or, if you give an argument to **''.schema''** because you only want the schema for a single table, the query looks like this:
<code sql> <code sql>
Line 293: Line 301:
</code> </code>
-The **%s** in the query above is replaced by the argument to ".schema", of course. Notice that the argument to the ".schema" command appears to the right of an SQL LIKE operator. So you can use wildcards in the name of the table. For example, to get the schema for all tables whose names contain the character string "abc" you could enter:+The **%s** in the query above is replaced by the argument to **''.schema''**, of course. Notice that the argument to the **''.schema''** command appears to the right of an SQL LIKE operator. So you can use wildcards in the name of the table. For example, to get the schema for all tables whose names contain the character string "abc" you could enter:
<code>sqlite> .schema %abc%</code> <code>sqlite> .schema %abc%</code>
-Along these same lines, the ".table" command also accepts a pattern as its first argument. If you give an argument to the .table command, a "%" is both appended and prepended and a LIKE clause is added to the query. This allows you to list only those tables that match a particular pattern.+Along these same lines, the **''.table''** command also accepts a pattern as its first argument. If you give an argument to the **''.table''** command, a "%" is both appended and prepended and a LIKE clause is added to the query. This allows you to list only those tables that match a particular pattern.
-The ".databases" command shows a list of all databases open in the current connection. There will always be at least 2. The first one is "main", the original database opened. The second is "temp", the database used for temporary tables. There may be additional databases listed for databases attached using the ATTACH statement. The first output column is the name the database is attached with, and the second column is the filename of the external file.+The **''.databases''** command shows a list of all databases open in the current connection. There will always be at least 2. The first one is "main", the original database opened. The second is "temp", the database used for temporary tables. There may be additional databases listed for databases attached using the ATTACH statement. The first output column is the name the database is attached with, and the second column is the filename of the external file.
-<code>sqlite> .databases&lt;/code>+<code> 
 +C:\TEMP> sqlite ex1.db 
 +SQLite version 2.8.17 
 +Enter &quot;.help" for instructions 
 +sqlite> .databases 
 +seq  name             file
 +---  ---------------  ---------------------------------
 +0    main             C:\TEMP\ex1.db
 +1    temp             C:\TEMP\sqlite_wk2nfpGbeTwPGOz
 +
 +sqlite>
 +</code>
Line 310: Line 329:
==== Converting An Entire Database To An ASCII Text File ==== ==== Converting An Entire Database To An ASCII Text File ====
-Use the ".dump" command to convert the entire contents of a database into a single ASCII text file. This file can be converted back into a database by piping it back into **sqlite**.+Use the **''.dump''** command to convert the entire contents of a database into a single ASCII text file. This file can be converted back into a database by piping it back into **''sqlite''**.
A good way to make an archival copy of a database is this: A good way to make an archival copy of a database is this:
Line 316: Line 335:
<code bash>$ echo '.dump' | sqlite ex1 | gzip -c >ex1.dump.gz</code> <code bash>$ echo '.dump' | sqlite ex1 | gzip -c >ex1.dump.gz</code>
-This generates a file named **ex1.dump.gz** that contains everything you need to reconstruct the database at a later time, or on another machine. To reconstruct the database, just type:+This generates a file named **''ex1.dump.gz''** that contains everything you need to reconstruct the database at a later time, or on another machine. To reconstruct the database, just type:
<code bash>$ zcat ex1.dump.gz | sqlite ex2</code> <code bash>$ zcat ex1.dump.gz | sqlite ex2</code>
-The text format used is the same as used by <nowiki>PostgreSQL</nowiki>, so you can also use the .dump command to export an SQLite database into a <nowiki>PostgreSQL</nowiki> database. Like this:+The text format used is the same as used by %%PostgreSQL%%, so you can also use the **''.dump''** command to export an SQLite database into a %%PostgreSQL%% database. Like this:
<code bash> <code bash>
Line 327: Line 346:
</code> </code>
-You can almost (but not quite) go the other way and export a <nowiki>PostgreSQL</nowiki> database into SQLite using the **pg_dump** utility. Unfortunately, when **pg_dump** writes the database schema information, it uses some SQL syntax that SQLite does not understand. So you cannot pipe the output of **pg_dump** directly into **sqlite**. But if you can recreate the schema separately, you can use **pg_dump** with the **-a** option to list just the data of a <nowiki>PostgreSQL</nowiki> database and import that directly into SQLite.+You can almost (but not quite) go the other way and export a %%PostgreSQL%% database into SQLite using the **pg_dump** utility. Unfortunately, when **pg_dump** writes the database schema information, it uses some SQL syntax that SQLite does not understand. So you cannot pipe the output of **pg_dump** directly into **''sqlite''**. But if you can recreate the schema separately, you can use **pg_dump** with the **-a** option to list just the data of a %%PostgreSQL%% database and import that directly into SQLite.
<code bash> <code bash>
Line 333: Line 352:
$ pg_dump -a ex2 | sqlite ex3 $ pg_dump -a ex2 | sqlite ex3
</code> </code>
 +
Line 338: Line 358:
==== Other Dot Commands ==== ==== Other Dot Commands ====
-The ".explain" dot command can be used to set the output mode to "column" and to set the column widths to values that are reasonable for looking at the output of an EXPLAIN command. The EXPLAIN command is an SQLite-specific SQL extension that is useful for debugging. If any regular SQL is prefaced by EXPLAIN, then the SQL command is parsed and analyzed but is not executed. Instead, the sequence of virtual machine instructions that would have been used to execute the SQL command are returned like a query result. For example:+The **''.explain''** dot command can be used to set the output mode to **column** and to set the column widths to values that are reasonable for looking at the output of an EXPLAIN command. The EXPLAIN command is an SQLite-specific SQL extension that is useful for debugging. If any regular SQL is prefaced by EXPLAIN, then the SQL command is parsed and analyzed but is not executed. Instead, the sequence of virtual machine instructions that would have been used to execute the SQL command are returned like a query result. For example:
<code> <code>
Line 344: Line 364:
sqlite> explain delete from tbl1 where two<20; sqlite> explain delete from tbl1 where two<20;
addr  opcode        p1          p2          p3 addr  opcode        p1          p2          p3
-----  ------------  ----------  ----------  -----------------------------------+----  ------------  ----------  ----------  ----------
0     Transaction   0           0 0     Transaction   0           0
1     VerifyCookie  0           180 1     VerifyCookie  0           180
Line 373: Line 393:
</code> </code>
-The ".timeout" command sets the amount of time that the **sqlite** program will wait for locks to clear on files it is trying to access before returning an error. The default value of the timeout is zero so that an error is returned immediately if any needed database table or index is locked.+The **''.timeout''** command sets the amount of time that the **''sqlite''** program will wait for locks to clear on files it is trying to access before returning an error. The default value of the timeout is zero so that an error is returned immediately if any needed database table or index is locked. 
 + 
 +And finally, we mention the **''.exit''** command which causes the **''sqlite''** program to exit (**''.quit''** and **''.q''** can also be used to exit). 
-And finally, we mention the ".exit" command which causes the sqlite program to exit. 
==== Using sqlite in a shell script ==== ==== Using sqlite in a shell script ====
-One way to use sqlite in a shell script is to use "echo" or "cat" to generate a sequence of commands in a file, then invoke sqlite while redirecting input from the generated command file. This works fine and is appropriate in many circumstances. But as an added convenience, sqlite allows a single SQL command to be entered on the command line as a second argument after the database name. When the sqlite program is launched with two arguments, the second argument is passed to the SQLite library for processing, the query results are printed on standard output in list mode, and the program exits. This mechanism is designed to make sqlite easy to use in conjunction with programs like "awk". For example:+One way to use **''sqlite''** in a shell script is to use **''echo''** or **''cat''** to generate a sequence of commands in a file, then invoke **''sqlite''** while redirecting input from the generated command file. This works fine and is appropriate in many circumstances. But as an added convenience, **''sqlite''** allows a single SQL command to be entered on the command line as a second argument after the database name. When the **''sqlite''** program is launched with two arguments, the second argument is passed to the SQLite library for processing, the query results are printed on standard output in list mode, and the program exits. This mechanism is designed to make **''sqlite''** easy to use in conjunction with programs like **''awk''**. For example:
<code bash> <code bash>
Line 387: Line 409:
<tr><td>goodbye<td>20 <tr><td>goodbye<td>20
$</code> $</code>
 +
Line 392: Line 415:
SQLite commands are normally terminated by a semicolon. In the shell you can also use the word "GO" (case-insensitive) or a backslash character "\" on a line by itself to end a command. These are used by SQL Server and Oracle, respectively. These won't work in **sqlite_exec()**, because the shell translates these into a semicolon before passing them to that function. SQLite commands are normally terminated by a semicolon. In the shell you can also use the word "GO" (case-insensitive) or a backslash character "\" on a line by itself to end a command. These are used by SQL Server and Oracle, respectively. These won't work in **sqlite_exec()**, because the shell translates these into a semicolon before passing them to that function.
 +
 +
==== Compiling the sqlite program from sources ==== ==== Compiling the sqlite program from sources ====
-The sqlite program is built automatically when you compile the sqlite library. Just get a copy of the source tree, run "configure" and then "make".+The **''sqlite''** program is built automatically when you compile the SQLite library. Just get a copy of the source tree, run **''configure''** and then **''make''**. 
 
howtos/sqlite_tutorial.1169514486.txt.gz · Last modified: 2008/02/08 19:49 (external edit)

Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.

Recent changes RSS feed Donate Driven by DokuWiki
The content of this wiki is protected by the GNU Fee Documentation License