Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Additional docs |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | sourceforge |
| Files: | files | file ages | folders |
| SHA1: |
61e01b2074ef6e1b4b12a7c6a3504586 |
| User & Date: | rmsimpson 2006-09-08 21:31:46 |
Context
|
2006-09-09
| ||
| 15:28 | 1.0.34.0 check-in: c57b635c6b user: rmsimpson tags: sourceforge | |
|
2006-09-08
| ||
| 21:31 | Additional docs check-in: 61e01b2074 user: rmsimpson tags: sourceforge | |
| 20:18 | 1.0.35.0 check-in: 76248530ca user: rmsimpson tags: sourceforge | |
Changes
Added Doc/Extra/blank.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>[Title Goes Here]</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">[Running Header]</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">[Header Row]</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading">[H1 Header]</h1> 57 + <p> 58 + [Document Text] 59 + </p> 60 + <h4> 61 + [Sub Section]</h4> 62 + <p> 63 + [Sub Section Text] 64 + </p> 65 + <hr> 66 + <div id="footer"> 67 + <p> 68 + </p> 69 + <p> 70 + </p> 71 + </div> 72 + </div> 73 + </div> 74 + </body> 75 +</html>
Added Doc/Extra/lang_altertable.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>ALTER TABLE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">ALTER TABLE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + ALTER TABLE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">ALTER TABLE </font></b>[<b><font color="#2c2cf0"></font></b><i><font 67 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 68 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table-name</font></i><b><font 69 + color="#2c2cf0"> </font></b><i><font color="#ff3434">alteration</font></i><b><font 70 + color="#2c2cf0"></font></b></td> 71 + </tr> 72 + <tr> 73 + <td align="right" valign="top"> 74 + <i><font color="#ff3434">alteration</font></i> ::=</td> 75 + <td> 76 + <b><font color="#2c2cf0">RENAME TO </font></b><i><font color="#ff3434">new-table-name</font></i><b><font 77 + color="#2c2cf0"></font></b></td> 78 + </tr> 79 + <tr> 80 + <td align="right" valign="top"> 81 + <i><font color="#ff3434">alteration</font></i> ::=</td> 82 + <td> 83 + <b><font color="#2c2cf0">ADD </font></b>[<b><font color="#2c2cf0">COLUMN</font></b>]<b><font 84 + color="#2c2cf0"> </font></b><i><font color="#ff3434">column-def</font></i><b><font 85 + color="#2c2cf0"></font></b></td> 86 + </tr> 87 + </table> 88 + </p> 89 + <p> 90 + SQLite's version of the ALTER TABLE command allows the user to rename or add a new 91 + column to an existing table. It is not possible to remove a column from a table. 92 + </p> 93 + <p> 94 + The RENAME TO syntax is used to rename the table identified by <i>[database-name.]table-name</i> 95 + to <i>new-table-name</i>. This command cannot be used to move a table between attached 96 + databases, only to rename a table within the same database.</p> 97 + <p> 98 + If the table being renamed has triggers or indices, then these remain attached to 99 + the table after it has been renamed. However, if there are any view definitions, 100 + or statements executed by triggers that refer to the table being renamed, these 101 + are not automatically modified to use the new table name. If this is required, the 102 + triggers or view definitions must be dropped and recreated to use the new table 103 + name by hand. 104 + </p> 105 + <p> 106 + The ADD [COLUMN] syntax is used to add a new column to an existing table. The new 107 + column is always appended to the end of the list of existing columns. <i>Column-def</i> 108 + may take any of the forms permissable in a CREATE TABLE statement, with the following 109 + restrictions: 110 + </p> 111 + <ul> 112 + <li>The column may not have a PRIMARY KEY or UNIQUE constraint. </li> 113 + <li>The column may not have a default value of CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP. 114 + </li> 115 + <li>If a NOT NULL constraint is specified, then the column must have a default value 116 + other than NULL. </li> 117 + </ul> 118 + <p> 119 + The execution time of the ALTER TABLE command is independent of the amount of data 120 + in the table. The ALTER TABLE command runs as quickly on a table with 10 million 121 + rows as it does on a table with 1 row. 122 + </p> 123 + <p> 124 + After ADD COLUMN has been run on a database, that database will not be readable 125 + by SQLite version 3.1.3 and earlier until the database is <a href="lang_vacuum.html"> 126 + VACUUM</a>ed.</p> 127 + <p> 128 + </p> 129 + <hr> 130 + <div id="footer"> 131 + <p> 132 + </p> 133 + <p> 134 + </p> 135 + </div> 136 + </div> 137 + </div> 138 + </body> 139 +</html>
Added Doc/Extra/lang_analyze.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>ANALYZE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">ANALYZE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + ANALYZE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">ANALYZE</font></b></td> 67 + </tr> 68 + </table> 69 + <table cellpadding="10"> 70 + <tr> 71 + <td align="right" valign="top"> 72 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 73 + <td> 74 + <b><font color="#2c2cf0">ANALYZE </font></b><i><font color="#ff3434">database-name</font></i><b><font 75 + color="#2c2cf0"></font></b></td> 76 + </tr> 77 + </table> 78 + <table cellpadding="10"> 79 + <tr> 80 + <td align="right" valign="top"> 81 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 82 + <td> 83 + <b><font color="#2c2cf0">ANALYZE </font></b>[<b><font color="#2c2cf0"></font></b><i><font 84 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 85 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table-name</font></i><b><font 86 + color="#2c2cf0"></font></b></td> 87 + </tr> 88 + </table> 89 + </p> 90 + <p> 91 + The ANALYZE command gathers statistics about indices and stores them in a special 92 + tables in the database where the query optimizer can use them to help make better 93 + index choices. If no arguments are given, all indices in all attached databases 94 + are analyzed. If a database name is given as the argument, all indices in that one 95 + database are analyzed. If the argument is a table name, then only indices associated 96 + with that one table are analyzed.</p> 97 + <p> 98 + The initial implementation stores all statistics in a single table named <b>sqlite_stat1</b>. 99 + Future enhancements may create additional tables with the same name pattern except 100 + with the "1" changed to a different digit. The <b>sqlite_stat1</b> table cannot be <a href="lang_droptable.html">DROP</a>ped, but all the content can be <a href="lang_delete.html"> 101 + DELETE</a>d which has the same effect.</p> 102 + <p> 103 + <hr> 104 + </p> 105 + <div id="footer"> 106 + <p> 107 + </p> 108 + <p> 109 + </p> 110 + </div> 111 + </div> 112 + </div> 113 + </body> 114 +</html>
Added Doc/Extra/lang_attach.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>ATTACH DATABASE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">ATTACH DATABASE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + ATTACH DATABASE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">ATTACH </font></b>[<b><font color="#2c2cf0">DATABASE</font></b>]<b><font 67 + color="#2c2cf0"> </font></b><i><font color="#ff3434">database-filename</font></i><b><font 68 + color="#2c2cf0"> AS </font></b><i><font color="#ff3434">database-name</font></i><b><font 69 + color="#2c2cf0"></font></b></td> 70 + </tr> 71 + </table> 72 + </p> 73 + <p> 74 + The ATTACH DATABASE statement adds another database file to the current database 75 + connection. If the filename contains punctuation characters it must be quoted. The 76 + names 'main' and 'temp' refer to the main database and the database used for temporary 77 + tables. These cannot be detached. Attached databases are removed using the <a href="lang_detach.html"> 78 + DETACH DATABASE</a> statement.</p> 79 + <p> 80 + You can read from and write to an attached database and you can modify the schema 81 + of the attached database. This is a new feature of SQLite version 3.0. In SQLite 82 + 2.8, schema changes to attached databases were not allowed.</p> 83 + <p> 84 + You cannot create a new table with the same name as a table in an attached database, 85 + but you can attach a database which contains tables whose names are duplicates of 86 + tables in the main database. It is also permissible to attach the same database 87 + file multiple times.</p> 88 + <p> 89 + Tables in an attached database can be referred to using the syntax <i>database-name.table-name</i>. 90 + If an attached table doesn't have a duplicate table name in the main database, it 91 + doesn't require a database name prefix. When a database is attached, all of its 92 + tables which don't have duplicate names become the default table of that name. Any 93 + tables of that name attached afterwards require the table prefix. If the default 94 + table of a given name is detached, then the last table of that name attached becomes 95 + the new default.</p> 96 + <p> 97 + Transactions involving multiple attached databases are atomic, assuming that the 98 + main database is not ":memory:". If the main database is ":memory:" then transactions 99 + continue to be atomic within each individual database file. But if the host computer 100 + crashes in the middle of a COMMIT where two or more database files are updated, 101 + some of those files might get the changes where others might not. Atomic commit 102 + of attached databases is a new feature of SQLite version 3.0. In SQLite version 103 + 2.8, all commits to attached databases behaved as if the main database were ":memory:". 104 + </p> 105 + <p> 106 + There is a compile-time limit of 10 attached database files.</p> 107 + <p> 108 + <hr> 109 + </p> 110 + <div id="footer"> 111 + <p> 112 + </p> 113 + <p> 114 + </p> 115 + </div> 116 + </div> 117 + </div> 118 + </body> 119 +</html>
Added Doc/Extra/lang_comment.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>comment</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">comment</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + comment</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">comment</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">SQL-comment</font></i><b><font 67 + color="#2c2cf0"> </font></b><big>|</big><b><font color="#2c2cf0"> </font></b><i><font 68 + color="#ff3434">C-comment</font></i><b><font color="#2c2cf0"></font></b></td> 69 + </tr> 70 + <tr> 71 + <td align="right" valign="top"> 72 + <i><font color="#ff3434">SQL-comment</font></i> ::=</td> 73 + <td> 74 + <b><font color="#2c2cf0">-- </font></b><i><font color="#ff3434">single-line</font></i><b><font 75 + color="#2c2cf0"></font></b></td> 76 + </tr> 77 + <tr> 78 + <td align="right" valign="top"> 79 + <i><font color="#ff3434">C-comment</font></i> ::=</td> 80 + <td> 81 + <b><font color="#2c2cf0">/<big>*</big> </font></b><i><font color="#ff3434">multiple-lines</font></i><b><font 82 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"><big>*</big>/</font></b>]<b><font 83 + color="#2c2cf0"></font></b></td> 84 + </tr> 85 + </table> 86 + </p> 87 + <p> 88 + Comments aren't SQL commands, but can occur in SQL queries. They are treated as 89 + whitespace by the parser. They can begin anywhere whitespace can be found, including 90 + inside expressions that span multiple lines. 91 + </p> 92 + <p> 93 + SQL comments only extend to the end of the current line.</p> 94 + <p> 95 + C comments can span any number of lines. If there is no terminating delimiter, they 96 + extend to the end of the input. This is not treated as an error. A new SQL statement 97 + can begin on a line after a multiline comment ends. C comments can be embedded anywhere 98 + whitespace can occur, including inside expressions, and in the middle of 99 + other SQL 100 + statements. C comments do not nest. SQL comments inside a C comment will be ignored. 101 + </p> 102 + <p> 103 + <hr> 104 + </p> 105 + <div id="footer"> 106 + <p> 107 + </p> 108 + <p> 109 + </p> 110 + </div> 111 + </div> 112 + </div> 113 + </body> 114 +</html>
Added Doc/Extra/lang_conflict.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>ON CONFLICT</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">ON CONFLICT clause</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + ON CONFLICT clause</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">conflict-clause</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">ON CONFLICT </font></b><i><font color="#ff3434">conflict-algorithm</font></i><b><font 67 + color="#2c2cf0"></font></b></td> 68 + </tr> 69 + <tr> 70 + <td align="right" valign="top"> 71 + <i><font color="#ff3434">conflict-algorithm</font></i> ::=</td> 72 + <td> 73 + <b><font color="#2c2cf0">ROLLBACK </font></b><big>|</big><b><font color="#2c2cf0"> 74 + ABORT </font></b><big>|</big><b><font color="#2c2cf0"> FAIL </font></b><big>|</big><b><font 75 + color="#2c2cf0"> IGNORE </font></b><big>|</big><b><font color="#2c2cf0"> REPLACE</font></b></td> 76 + </tr> 77 + </table> 78 + </p> 79 + <p> 80 + The ON CONFLICT clause is not a separate SQL command. It is a non-standard clause 81 + that can appear in many 82 + other SQL commands. It is given its own section in this 83 + document because it is not part of standard SQL and therefore might not be familiar.</p> 84 + <p> 85 + The syntax for the ON CONFLICT clause is as shown above for the CREATE TABLE command. 86 + For the INSERT and UPDATE commands, the keywords "ON CONFLICT" are replaced by "OR", 87 + to make the syntax seem more natural. For example, instead of "INSERT ON CONFLICT 88 + IGNORE" we have "INSERT OR IGNORE". The keywords change but the meaning of the clause 89 + is the same either way.</p> 90 + <p> 91 + The ON CONFLICT clause specifies an algorithm used to resolve constraint conflicts. 92 + There are five choices: ROLLBACK, ABORT, FAIL, IGNORE, and REPLACE. The default 93 + algorithm is ABORT. This is what they mean:</p> 94 + <dl> 95 + <dt><b>ROLLBACK</b> </dt> 96 + <dd> 97 + <p> 98 + When a constraint violation occurs, an immediate ROLLBACK occurs, thus ending the 99 + current transaction, and the command aborts with a return code of SQLITE_CONSTRAINT. 100 + If no transaction is active (other than the implied transaction that is created 101 + on every command) then this algorithm works the same as ABORT.</p> 102 + </dd> 103 + <dt><b>ABORT</b> </dt> 104 + <dd> 105 + <p> 106 + When a constraint violation occurs, the command backs out any prior changes it might 107 + have made and aborts with a return code of SQLITE_CONSTRAINT. But no ROLLBACK is 108 + executed so changes from prior commands within the same transaction are preserved. 109 + This is the default behavior.</p> 110 + </dd> 111 + <dt><b>FAIL</b> </dt> 112 + <dd> 113 + <p> 114 + When a constraint violation occurs, the command aborts with a return code SQLITE_CONSTRAINT. 115 + But any changes to the database that the command made prior to encountering the 116 + constraint violation are preserved and are not backed out. For example, if an UPDATE 117 + statement encountered a constraint violation on the 100th row that it attempts to 118 + update, then the first 99 row changes are preserved but changes to rows 100 and 119 + beyond never occur.</p> 120 + </dd> 121 + <dt><b>IGNORE</b> </dt> 122 + <dd> 123 + <p> 124 + When a constraint violation occurs, the one row that contains the constraint violation 125 + is not inserted or changed. But the command continues executing normally. Other 126 + rows before and after the row that contained the constraint violation continue to 127 + be inserted or updated normally. No error is returned.</p> 128 + </dd> 129 + <dt><b>REPLACE</b> </dt> 130 + <dd> 131 + <p> 132 + When a UNIQUE constraint violation occurs, the pre-existing rows that are causing 133 + the constraint violation are removed prior to inserting or updating the current 134 + row. Thus the insert or update always occurs. The command continues executing normally. 135 + No error is returned. If a NOT NULL constraint violation occurs, the NULL value 136 + is replaced by the default value for that column. If the column has no default value, 137 + then the ABORT algorithm is used. If a CHECK constraint violation occurs then the 138 + IGNORE algorithm is used.</p> 139 + <p> 140 + When this conflict resolution strategy deletes rows in order to satisfy a constraint, 141 + it does not invoke delete triggers on those rows. This behavior might change in 142 + a future release.</p> 143 + </dd> 144 + </dl> 145 + <p> 146 + The algorithm specified in the OR clause of a INSERT or UPDATE overrides any algorithm 147 + specified in a CREATE TABLE. If no algorithm is specified anywhere, the ABORT algorithm 148 + is used.</p> 149 + <p> 150 + <hr> 151 + </p> 152 + <div id="footer"> 153 + <p> 154 + </p> 155 + <p> 156 + </p> 157 + </div> 158 + </div> 159 + </div> 160 + </body> 161 +</html>
Added Doc/Extra/lang_createindex.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>CREATE INDEX</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">CREATE INDEX</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + CREATE INDEX</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">CREATE </font></b>[<b><font color="#2c2cf0">UNIQUE</font></b>]<b><font 67 + color="#2c2cf0"> INDEX </font></b>[<b><font color="#2c2cf0">IF NOT EXISTS</font></b>]<b><font 68 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 69 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 70 + <i><font color="#ff3434">index-name</font></i><b><font color="#2c2cf0"> 71 + <br /> 72 + ON </font></b><i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> 73 + <big>(</big> </font></b><i><font color="#ff3434">column-name</font></i><b><font color="#2c2cf0"> 74 + </font></b>[<b><font color="#2c2cf0"><big>,</big> </font></b><i><font color="#ff3434"> 75 + column-name</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b><big>*</big><b><font 76 + color="#2c2cf0"> <big>)</big></font></b></td> 77 + </tr> 78 + <tr> 79 + <td align="right" valign="top"> 80 + <i><font color="#ff3434">column-name</font></i> ::=</td> 81 + <td> 82 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">name</font></i><b><font 83 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"> COLLATE </font></b><i><font 84 + color="#ff3434">collation-name</font></i><b><font color="#2c2cf0"></font></b>]<b><font 85 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"> ASC </font></b><big>|</big><b><font 86 + color="#2c2cf0"> DESC </font></b>]<b><font color="#2c2cf0"></font></b></td> 87 + </tr> 88 + </table> 89 + </p> 90 + <p> 91 + The CREATE INDEX command consists of the keywords "CREATE INDEX" followed by the 92 + name of the new index, the keyword "ON", the name of a previously created table 93 + that is to be indexed, and a parenthesized list of names of columns in the table 94 + that are used for the index key. Each column name can be followed by one of the 95 + "ASC" or "DESC" keywords to indicate sort order, but the sort order is ignored in 96 + the current implementation. Sorting is always done in ascending order.</p> 97 + <p> 98 + The COLLATE clause following each column name defines a collating sequence used 99 + for text entires in that column. The default collating sequence is the collating 100 + sequence defined for that column in the CREATE TABLE statement. Or if no collating 101 + sequence is otherwise defined, the built-in BINARY collating sequence is used.</p> 102 + <p> 103 + There are no arbitrary limits on the number of indices that can be attached to a 104 + single table, nor on the number of columns in an index.</p> 105 + <p> 106 + If the UNIQUE keyword appears between CREATE and INDEX then duplicate index entries 107 + are not allowed. Any attempt to insert a duplicate entry will result in an error.</p> 108 + <p> 109 + The exact text of each CREATE INDEX statement is stored in the <b>sqlite_master</b> 110 + or <b>sqlite_temp_master</b> table, depending on whether the table being indexed 111 + is temporary. Every time the database is opened, all CREATE INDEX statements are 112 + read from the <b>sqlite_master</b> table and used to regenerate 113 + SQLite's internal 114 + representation of the index layout.</p> 115 + <p> 116 + If the optional IF NOT EXISTS clause is present and another index with the same name aleady exists, then this command becomes a no-op.</p> 117 + <p> 118 + Indexes are removed with the <a href="lang_dropindex.html">DROP INDEX</a> command.</p> 119 + <p> 120 + <hr> 121 + </p> 122 + <div id="footer"> 123 + <p> 124 + </p> 125 + <p> 126 + </p> 127 + </div> 128 + </div> 129 + </div> 130 + </body> 131 +</html>
Added Doc/Extra/lang_createtable.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>CREATE TABLE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">CREATE TABLE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + CREATE TABLE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">CREATE </font></b>[<b><font color="#2c2cf0">TEMP </font></b> 67 + <big>|</big><b><font color="#2c2cf0"> TEMPORARY</font></b>]<b><font color="#2c2cf0"> 68 + TABLE </font></b>[<b><font color="#2c2cf0">IF NOT EXISTS</font></b>]<b><font color="#2c2cf0"> 69 + </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 70 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 71 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> <big>(</big><br /> 72 + </font></b><i><font color="#ff3434">column-def</font></i><b><font color="#2c2cf0"> 73 + </font></b>[<b><font color="#2c2cf0"><big>,</big> </font></b><i><font color="#ff3434"> 74 + column-def</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b><big>*</big><b><font 75 + color="#2c2cf0"><br /> 76 + </font></b>[<b><font color="#2c2cf0"><big>,</big> </font></b> 77 + <i><font color="#ff3434">constraint</font></i><b><font color="#2c2cf0"></font></b>]<b><font 78 + color="#2c2cf0"></font></b><big>*</big><b><font color="#2c2cf0"><br /> 79 + <big>)</big></font></b></td> 80 + </tr> 81 + <tr> 82 + <td align="right" valign="top"> 83 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 84 + <td> 85 + <b><font color="#2c2cf0">CREATE </font></b>[<b><font color="#2c2cf0">TEMP </font></b> 86 + <big>|</big><b><font color="#2c2cf0"> TEMPORARY</font></b>]<b><font color="#2c2cf0"> 87 + TABLE </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 88 + color="#2c2cf0"><big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 89 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> AS </font> 90 + </b><i><font color="#ff3434">select-statement</font></i><b><font color="#2c2cf0"></font></b></td> 91 + </tr> 92 + <tr> 93 + <td align="right" valign="top"> 94 + <i><font color="#ff3434">column-def</font></i> ::=</td> 95 + <td> 96 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">name</font></i><b><font 97 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">type</font></i><b><font 98 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b>[<b><font 99 + color="#2c2cf0">CONSTRAINT </font></b><i><font color="#ff3434">name</font></i><b><font 100 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font></b><i><font color="#ff3434"> 101 + column-constraint</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b><big>*</big><b><font 102 + color="#2c2cf0"></font></b></td> 103 + </tr> 104 + <tr> 105 + <td align="right" valign="top"> 106 + <i><font color="#ff3434">type</font></i> ::=</td> 107 + <td> 108 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">typename</font></i><b><font 109 + color="#2c2cf0"> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 110 + </font></b><i><font color="#ff3434">typename</font></i><b><font color="#2c2cf0"> <big> 111 + (</big> </font></b><i><font color="#ff3434">number</font></i><b><font color="#2c2cf0"> 112 + <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 113 + </font></b><i><font color="#ff3434">typename</font></i><b><font color="#2c2cf0"> <big> 114 + (</big> </font></b><i><font color="#ff3434">number</font></i><b><font color="#2c2cf0"> 115 + <big>,</big> </font></b><i><font color="#ff3434">number</font></i><b><font color="#2c2cf0"> 116 + <big>)</big></font></b></td> 117 + </tr> 118 + <tr> 119 + <td align="right" valign="top"> 120 + <i><font color="#ff3434">column-constraint</font></i> ::=</td> 121 + <td> 122 + <b><font color="#2c2cf0">NOT NULL </font></b>[<b><font color="#2c2cf0"> </font></b> 123 + <i><font color="#ff3434">conflict-clause</font></i><b><font color="#2c2cf0"> </font> 124 + </b>]<b><font color="#2c2cf0"> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 125 + PRIMARY KEY </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">sort-order</font></i><b><font 126 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"> 127 + </font></b><i><font color="#ff3434">conflict-clause</font></i><b><font color="#2c2cf0"> 128 + </font></b>]<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0">AUTOINCREMENT</font></b>]<b><font 129 + color="#2c2cf0"> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 130 + UNIQUE </font></b>[<b><font color="#2c2cf0"> </font></b><i><font color="#ff3434">conflict-clause</font></i><b><font 131 + color="#2c2cf0"> </font></b>]<b><font color="#2c2cf0"> </font></b><big>|</big><b><font 132 + color="#2c2cf0"><br /> 133 + CHECK <big>(</big> </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 134 + <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 135 + DEFAULT </font></b><i><font color="#ff3434">value</font></i><b><font color="#2c2cf0"> 136 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 137 + COLLATE </font></b><i><font color="#ff3434">collation-name</font></i><b><font color="#2c2cf0"></font></b></td> 138 + </tr> 139 + <tr> 140 + <td align="right" valign="top"> 141 + <i><font color="#ff3434">constraint</font></i> ::=</td> 142 + <td> 143 + <b><font color="#2c2cf0">PRIMARY KEY <big>(</big> </font></b><i><font color="#ff3434"> 144 + column-list</font></i><b><font color="#2c2cf0"> <big>)</big> </font></b>[<b><font 145 + color="#2c2cf0"> </font></b><i><font color="#ff3434">conflict-clause</font></i><b><font 146 + color="#2c2cf0"> </font></b>]<b><font color="#2c2cf0"> </font></b><big>|</big><b><font 147 + color="#2c2cf0"><br /> 148 + UNIQUE <big>(</big> </font></b><i><font color="#ff3434">column-list</font></i><b><font 149 + color="#2c2cf0"> <big>)</big> </font></b>[<b><font color="#2c2cf0"> </font></b> 150 + <i><font color="#ff3434">conflict-clause</font></i><b><font color="#2c2cf0"> </font> 151 + </b>]<b><font color="#2c2cf0"> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 152 + CHECK <big>(</big> </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 153 + <big>)</big></font></b></td> 154 + </tr> 155 + <tr> 156 + <td align="right" valign="top"> 157 + <i><font color="#ff3434">conflict-clause</font></i> ::=</td> 158 + <td> 159 + <b><font color="#2c2cf0">ON CONFLICT </font></b><i><font color="#ff3434">conflict-algorithm</font></i><b><font 160 + color="#2c2cf0"></font></b></td> 161 + </tr> 162 + </table> 163 + </p> 164 + <p> 165 + A CREATE TABLE statement is basically the keywords "CREATE TABLE" followed by the 166 + name of a new table and a parenthesized list of column definitions and constraints. 167 + The table name can be either an identifier or a string. Tables names that begin 168 + with "<b>sqlite_</b>" are reserved for use by the engine.</p> 169 + <p> 170 + Each column definition is the name of the column followed by the datatype for that 171 + column, then one or more optional column constraints. The datatype for the column 172 + does not restrict what data may be put in that column. See <a href="http://www.sqlite.org/datatype3.html"> 173 + Datatypes In SQLite Version 3</a> for additional information. The UNIQUE constraint 174 + causes an index to be created on the specified columns. This index must contain 175 + unique keys. The COLLATE clause specifies what text <a href="http://www.sqlite.org/datatype3.html#collation"> 176 + collating function</a> to use when comparing text entries for the column. The 177 + built-in BINARY collating function is used by default. 178 + </p> 179 + <p> 180 + The DEFAULT constraint specifies a default value to use when doing an INSERT. The 181 + value may be NULL, a string constant or a number. Starting with version 3.1.0, the 182 + default value may also be one of the special case-independant keywords CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP. If the value is NULL, a string constant or number, 183 + it is literally inserted into the column whenever an INSERT statement that does 184 + not specify a value for the column is executed. If the value is CURRENT_TIME, CURRENT_DATE 185 + or CURRENT_TIMESTAMP, then the current UTC date and/or time is inserted into the 186 + columns. For CURRENT_TIME, the format is HH:MM:SS. For CURRENT_DATE, YYYY-MM-DD. 187 + The format for CURRENT_TIMESTAMP is "YYYY-MM-DD HH:MM:SS". 188 + </p> 189 + <p> 190 + Specifying a PRIMARY KEY normally just creates a UNIQUE index on the corresponding 191 + columns. However, if primary key is on a single column that has datatype INTEGER, 192 + then that column is used internally as the actual key of the B-Tree for the table. 193 + This means that the column may only hold unique integer values. (Except for this 194 + one case, SQLite ignores the datatype specification of columns and allows any kind 195 + of data to be put in a column regardless of its declared datatype.) If a table does 196 + not have an INTEGER PRIMARY KEY column, then the B-Tree key will be a automatically 197 + generated integer. The B-Tree key for a row can always be accessed using one of 198 + the special names "<b>ROWID</b>", "<b>OID</b>", or "<b>_ROWID_</b>". This is true 199 + regardless of whether or not there is an INTEGER PRIMARY KEY. An INTEGER PRIMARY 200 + KEY column man also include the keyword AUTOINCREMENT. The AUTOINCREMENT keyword 201 + modified the way that B-Tree keys are automatically generated. Additional detail 202 + on automatic B-Tree key generation is available <a href="http://www.sqlite.org/autoinc.html"> 203 + separately</a>.</p> 204 + <p> 205 + If the "TEMP" or "TEMPORARY" keyword occurs in between "CREATE" and "TABLE" then 206 + the table that is created is only visible within that same database connection and 207 + is automatically deleted when the database connection is closed. Any indices created 208 + on a temporary table are also temporary. Temporary tables and indices are stored 209 + in a separate file distinct from the main database file.</p> 210 + <p> 211 + If a <database-name> is specified, then the table is created in the named 212 + database. It is an error to specify both a <database-name> and the TEMP keyword, 213 + unless the <database-name> is "temp". If no database name is specified, and 214 + the TEMP keyword is not present, the table is created in the main database.</p> 215 + <p> 216 + The optional conflict-clause following each constraint allows the specification 217 + of an alternative default constraint conflict resolution algorithm for that constraint. The default is abort ABORT. Different constraints within the same table may have 218 + different default conflict resolution algorithms. If an COPY, INSERT, or UPDATE 219 + command specifies a different conflict resolution algorithm, then that algorithm 220 + is used in place of the default algorithm specified in the CREATE TABLE statement. 221 + See the section titled <a href="lang_conflict.html">ON CONFLICT</a> for additional 222 + information.</p> 223 + <p> 224 + CHECK constraints are supported as of version 3.3.0. Prior to version 3.3.0, CHECK 225 + constraints were parsed but not enforced.</p> 226 + <p> 227 + There are no arbitrary limits on the number of columns or on the number of constraints 228 + in a table. The total amount of data in a single row is limited to about 1 megabytes 229 + in version 2.8. In version 3.0 there is no arbitrary limit on the amount of data 230 + in a row.</p> 231 + <p> 232 + The CREATE TABLE AS form defines the table to be the result set of a query. The 233 + names of the table columns are the names of the columns in the result.</p> 234 + <p> 235 + The exact text of each CREATE TABLE statement is stored in the <b>sqlite_master</b> 236 + table. Every time the database is opened, all CREATE TABLE statements are read from 237 + the <b>sqlite_master</b> table and used to regenerate 238 + SQLite's internal representation 239 + of the table layout. If the original command was a CREATE TABLE AS then then an 240 + equivalent CREATE TABLE statement is synthesized and store in <b>sqlite_master</b> 241 + in place of the original command. The text of CREATE TEMPORARY TABLE statements 242 + are stored in the <b>sqlite_temp_master</b> table. 243 + </p> 244 + <p> 245 + If the optional IF NOT EXISTS clause is present and another table with the same 246 + name aleady exists, then this command becomes a no-op.</p> 247 + <p> 248 + Tables are removed using the <a href="lang_droptable.html">DROP TABLE</a> statement. 249 + </p> 250 + <p> 251 + <hr> 252 + </p> 253 + <div id="footer"> 254 + <p> 255 + </p> 256 + <p> 257 + </p> 258 + </div> 259 + </div> 260 + </div> 261 + </body> 262 +</html>
Added Doc/Extra/lang_createtrigger.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>CREATE TABLE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">CREATE TRIGGER</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + CREATE TRIGGER</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">CREATE </font></b>[<b><font color="#2c2cf0">TEMP </font></b> 67 + <big>|</big><b><font color="#2c2cf0"> TEMPORARY</font></b>]<b><font color="#2c2cf0"> 68 + TRIGGER </font></b><i><font color="#ff3434">trigger-name</font></i><b><font color="#2c2cf0"> 69 + </font></b>[<b><font color="#2c2cf0"> BEFORE </font></b><big>|</big><b><font color="#2c2cf0"> 70 + AFTER </font></b>]<b><font color="#2c2cf0"><br /> 71 + </font></b><i><font color="#ff3434">database-event</font></i><b><font color="#2c2cf0"> 72 + ON </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 73 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 74 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"><br /> 75 + </font></b><i><font color="#ff3434">trigger-action</font></i><b><font color="#2c2cf0"></font></b></td> 76 + </tr> 77 + </table> 78 + <table cellpadding="10"> 79 + <tr> 80 + <td align="right" valign="top"> 81 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 82 + <td> 83 + <b><font color="#2c2cf0">CREATE </font></b>[<b><font color="#2c2cf0">TEMP </font></b> 84 + <big>|</big><b><font color="#2c2cf0"> TEMPORARY</font></b>]<b><font color="#2c2cf0"> 85 + TRIGGER </font></b><i><font color="#ff3434">trigger-name</font></i><b><font color="#2c2cf0"> 86 + INSTEAD OF<br /> 87 + </font></b><i><font color="#ff3434">database-event</font></i><b><font color="#2c2cf0"> 88 + ON </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 89 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 90 + <i><font color="#ff3434">view-name</font></i><b><font color="#2c2cf0"><br /> 91 + </font></b><i><font color="#ff3434">trigger-action</font></i><b><font color="#2c2cf0"></font></b></td> 92 + </tr> 93 + </table> 94 + <table cellpadding="10"> 95 + <tr> 96 + <td align="right" valign="top"> 97 + <i><font color="#ff3434">database-event</font></i> ::=</td> 98 + <td> 99 + <b><font color="#2c2cf0">DELETE </font></b><big>|</big><b><font color="#2c2cf0"> 100 + <br /> 101 + INSERT </font></b><big>|</big><b><font color="#2c2cf0"> 102 + <br /> 103 + UPDATE </font></b><big>|</big><b><font color="#2c2cf0"> 104 + <br /> 105 + UPDATE OF </font></b><i><font color="#ff3434">column-list</font></i><b><font color="#2c2cf0"></font></b></td> 106 + </tr> 107 + </table> 108 + <table cellpadding="10"> 109 + <tr> 110 + <td align="right" valign="top"> 111 + <i><font color="#ff3434">trigger-action</font></i> ::=</td> 112 + <td> 113 + <b><font color="#2c2cf0"></font></b>[<b><font color="#2c2cf0"> FOR EACH ROW </font> 114 + </b><big>|</big><b><font color="#2c2cf0"> FOR EACH STATEMENT </font></b>]<b><font 115 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"> WHEN </font></b><i><font color="#ff3434"> 116 + expression</font></i><b><font color="#2c2cf0"> </font></b>]<b><font color="#2c2cf0"> 117 + <br /> 118 + BEGIN 119 + <br /> 120 + </font></b><i><font color="#ff3434">trigger-step</font></i><b><font 121 + color="#2c2cf0"> ; </font></b>[<b><font color="#2c2cf0"> </font></b><i><font color="#ff3434"> 122 + trigger-step</font></i><b><font color="#2c2cf0"> ; </font></b>]<b><font color="#2c2cf0"></font></b><big>*</big><b><font 123 + color="#2c2cf0"><br /> 124 + END</font></b></td> 125 + </tr> 126 + </table> 127 + <table cellpadding="10"> 128 + <tr> 129 + <td align="right" valign="top"> 130 + <i><font color="#ff3434">trigger-step</font></i> ::=</td> 131 + <td> 132 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">update-statement</font></i><b><font 133 + color="#2c2cf0"> </font></b><big>|</big><b><font color="#2c2cf0"> </font></b><i><font 134 + color="#ff3434">insert-statement</font></i><b><font color="#2c2cf0"> </font></b> 135 + <big>|</big><b><font color="#2c2cf0"> 136 + <br /> 137 + </font></b><i><font color="#ff3434">delete-statement</font></i><b><font color="#2c2cf0"> 138 + </font></b><big>|</big><b><font color="#2c2cf0"> </font></b><i><font color="#ff3434"> 139 + select-statement</font></i><b><font color="#2c2cf0"></font></b></td> 140 + </tr> 141 + </table> 142 + </p> 143 + <p> 144 + The CREATE TRIGGER statement is used to add triggers to the database schema. Triggers 145 + are database operations (the <i>trigger-action</i>) that are automatically performed 146 + when a specified database event (the <i>database-event</i>) occurs. 147 + </p> 148 + <p> 149 + A trigger may be specified to fire whenever a DELETE, INSERT or UPDATE of a particular 150 + database table occurs, or whenever an UPDATE of one or more specified columns of 151 + a table are updated.</p> 152 + <p> 153 + At this time SQLite supports only FOR EACH ROW triggers, not FOR EACH STATEMENT 154 + triggers. Hence explicitly specifying FOR EACH ROW is optional. FOR EACH ROW implies 155 + that the SQL statements specified as <i>trigger-steps</i> may be executed (depending 156 + on the WHEN clause) for each database row being inserted, updated or deleted by 157 + the statement causing the trigger to fire.</p> 158 + <p> 159 + Both the WHEN clause and the <i>trigger-steps</i> may access elements of the row 160 + being inserted, deleted or updated using references of the form "NEW.<i>column-name</i>" 161 + and "OLD.<i>column-name</i>", where <i>column-name</i> is the name of a column from the table that the trigger is associated with. OLD and NEW references may only be 162 + used in triggers on <i>trigger-event</i>s for which they are relevant, as follows:</p> 163 + <p> 164 + <table border="0" cellpadding="10"> 165 + <tr> 166 + <td align="right" valign="top" width="120"> 167 + <i>INSERT</i></td> 168 + <td valign="top"> 169 + NEW references are valid</td> 170 + </tr> 171 + <tr> 172 + <td align="right" valign="top" width="120"> 173 + <i>UPDATE</i></td> 174 + <td valign="top"> 175 + NEW and OLD references are valid</td> 176 + </tr> 177 + <tr> 178 + <td align="right" valign="top" width="120"> 179 + <i>DELETE</i></td> 180 + <td valign="top"> 181 + OLD references are valid</td> 182 + </tr> 183 + </table> 184 + </p> 185 + <p> 186 + </p> 187 + <p> 188 + If a WHEN clause is supplied, the SQL statements specified as <i>trigger-steps</i> 189 + are only executed for 190 + rows for which the WHEN clause is true. If no WHEN clause 191 + is supplied, the SQL statements are executed for all rows.</p> 192 + <p> 193 + The specified <i>trigger-time</i> determines when the <i>trigger-steps</i> will 194 + be executed relative to the insertion, modification or removal of the associated 195 + row.</p> 196 + <p> 197 + An ON CONFLICT clause may be specified as part of an UPDATE or INSERT <i>trigger-step</i>. 198 + However if an ON CONFLICT clause is specified as part of the statement causing the 199 + trigger to fire, then this conflict handling policy is used instead.</p> 200 + <p> 201 + Triggers are automatically dropped when the table that they are associated with 202 + is dropped.</p> 203 + <p> 204 + Triggers may be created on views, as well as ordinary tables, by specifying INSTEAD 205 + OF in the CREATE TRIGGER statement. If one or more ON INSERT, ON DELETE or ON UPDATE 206 + triggers are defined on a view, then it is not an error to execute an INSERT, DELETE 207 + or UPDATE statement on the view, respectively. Thereafter, executing an INSERT, 208 + DELETE or UPDATE on the view causes the associated triggers to fire. The real tables 209 + underlying the view are not modified (except possibly explicitly, by a trigger program).</p> 210 + <p> 211 + <b>Example:</b></p> 212 + <p> 213 + Assuming that customer records are stored in the "customers" table, and that order 214 + records are stored in the "orders" table, the following trigger ensures that all 215 + associated orders are redirected when a customer changes his or her address:</p> 216 + <blockquote> 217 + <pre> 218 +CREATE TRIGGER update_customer_address UPDATE OF address ON customers 219 + BEGIN 220 + UPDATE orders SET address = new.address WHERE customer_name = old.name; 221 + END; 222 +</pre> 223 + </blockquote> 224 + <p> 225 + With this trigger installed, executing the statement:</p> 226 + <blockquote> 227 + <pre> 228 +UPDATE customers SET address = '1 Main St.' WHERE name = 'Jack Jones'; 229 +</pre> 230 + </blockquote> 231 + <p> 232 + causes the following to be automatically executed:</p> 233 + <blockquote> 234 + <pre> 235 +UPDATE orders SET address = '1 Main St.' WHERE customer_name = 'Jack Jones'; 236 +</pre> 237 + </blockquote> 238 + <p> 239 + Note that currently, triggers may behave oddly when created on tables with INTEGER 240 + PRIMARY KEY fields. If a BEFORE trigger program modifies the INTEGER PRIMARY KEY 241 + field of a row that will be subsequently updated by the statement that causes the 242 + trigger to fire, then the update may not occur. The workaround is to declare the 243 + table with a PRIMARY KEY column instead of an INTEGER PRIMARY KEY column.</p> 244 + <p> 245 + A special SQL function RAISE() may be used within a trigger-program, with the following 246 + syntax</p> 247 + <p> 248 + <table cellpadding="10"> 249 + <tr> 250 + <td align="right" valign="top"> 251 + <i><font color="#ff3434">raise-function</font></i> ::=</td> 252 + <td> 253 + <b><font color="#2c2cf0">RAISE <big>(</big> ABORT<big>,</big> </font></b><i><font 254 + color="#ff3434">error-message</font></i><b><font color="#2c2cf0"> <big>)</big> </font> 255 + </b><big>|</big><b><font color="#2c2cf0"> 256 + <br /> 257 + RAISE <big>(</big> FAIL<big>,</big> </font></b><i><font color="#ff3434">error-message</font></i><b><font 258 + color="#2c2cf0"> <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"> 259 + <br /> 260 + RAISE <big>(</big> ROLLBACK<big>,</big> </font></b><i><font color="#ff3434">error-message</font></i><b><font 261 + color="#2c2cf0"> <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"> 262 + <br /> 263 + RAISE <big>(</big> IGNORE <big>)</big></font></b></td> 264 + </tr> 265 + </table> 266 + </p> 267 + <p> 268 + When one of the first three forms is called during trigger-program execution, the 269 + specified ON CONFLICT processing is performed (either ABORT, FAIL or ROLLBACK) and 270 + the current query terminates. An error code of SQLITE_CONSTRAINT is returned to 271 + the user, along with the specified error message.</p> 272 + <p> 273 + When RAISE(IGNORE) is called, the remainder of the current trigger program, the 274 + statement that caused the trigger program to execute and any subsequent trigger 275 + programs that would of been executed are abandoned. No database changes are rolled 276 + back. If the statement that caused the trigger program to execute is itself part 277 + of a trigger program, then that trigger program resumes execution at the beginning 278 + of the next step. 279 + </p> 280 + <p> 281 + Triggers are removed using the <a href="lang_droptrigger.html">DROP TRIGGER</a> 282 + statement.</p> 283 + <p> 284 + <hr> 285 + </p> 286 + <div id="footer"> 287 + <p> 288 + </p> 289 + <p> 290 + </p> 291 + </div> 292 + </div> 293 + </div> 294 + </body> 295 +</html>
Added Doc/Extra/lang_createview.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>CREATE VIEW</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">CREATE VIEW</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + CREATE VIEW</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">CREATE </font></b>[<b><font color="#2c2cf0">TEMP </font></b> 67 + <big>|</big><b><font color="#2c2cf0"> TEMPORARY</font></b>]<b><font color="#2c2cf0"> 68 + VIEW </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 69 + color="#2c2cf0"><big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 70 + <i><font color="#ff3434">view-name</font></i><b><font color="#2c2cf0"> AS </font></b> 71 + <i><font color="#ff3434">select-statement</font></i><b><font color="#2c2cf0"></font></b></td> 72 + </tr> 73 + </table> 74 + </p> 75 + <p> 76 + The CREATE VIEW command assigns a name to a pre-packaged <a href="lang_select.html"> 77 + SELECT</a> statement. Once the view is created, it can be used in the FROM clause 78 + of another SELECT in place of a table name. 79 + </p> 80 + <p> 81 + If the "TEMP" or "TEMPORARY" keyword occurs in between "CREATE" and "VIEW" then 82 + the view that is created is only visible to the process that opened the database 83 + and is automatically deleted when the database is closed.</p> 84 + <p> 85 + If a <database-name> is specified, then the view is created in the named database. 86 + It is an error to specify both a <database-name> and the TEMP keyword, unless 87 + the <database-name> is "temp". If no database name is specified, and the TEMP 88 + keyword is not present, the table is created in the main database.</p> 89 + <p> 90 + You cannot COPY, DELETE, INSERT or UPDATE a view. Views are read-only in SQLite. 91 + However, in many cases you can use a <a href="lang_createtrigger.html">TRIGGER</a> 92 + on the view to accomplish the same thing. Views are removed with the <a href="lang_dropview.html"> 93 + DROP VIEW</a> command.</p> 94 + <p> 95 + <hr> 96 + </p> 97 + <div id="footer"> 98 + <p> 99 + </p> 100 + <p> 101 + </p> 102 + </div> 103 + </div> 104 + </div> 105 + </body> 106 +</html>
Added Doc/Extra/lang_createvtab.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>CREATE VIRTUAL TABLE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">CREATE VIRTUAL TABLE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + CREATE VIRTUAL TABLE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">CREATE VIRTUAL TABLE </font></b>[<b><font color="#2c2cf0"></font></b><i><font 67 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 68 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table-name</font></i><b><font 69 + color="#2c2cf0"> USING </font></b><i><font color="#ff3434">module-name</font></i><b><font 70 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"><big>(</big> </font></b> 71 + <i><font color="#ff3434">arguments</font></i><b><font color="#2c2cf0"> <big>)</big></font></b>]<b><font 72 + color="#2c2cf0"></font></b></td> 73 + </tr> 74 + </table> 75 + </p> 76 + <p> 77 + A virtual table is an interface to an external storage or computation engine that 78 + appears to be a table but does not actually store information in the database file.</p> 79 + <p> 80 + In general, you can do anything with a virtual table that can be done with an ordinary 81 + table, except that you cannot create triggers on a virtual table. Some virtual table 82 + implementations might impose additional restrictions. For example, many virtual 83 + tables are read-only.</p> 84 + <p> 85 + The <module-name> is the 86 + name of an object that implements the virtual table. 87 + The <module-name> must be registered with the SQLite database connection using 88 + <a href="capi3ref.html#sqlite3_create_module">sqlite3_create_module</a> prior to 89 + issuing the CREATE VIRTUAL TABLE statement. The module takes zero or more comma-separated 90 + arguments. The arguments can be just about any text as long as it has balanced parentheses. 91 + The argument syntax is sufficiently general that the arguments can be made to appear 92 + as column definitions in a traditional <a href="lang_createtable.html">CREATE TABLE</a> 93 + statement. SQLite passes the module arguments directly to the module without any 94 + interpretation. It is the responsibility of the module implementation to parse and 95 + interpret its own arguments.</p> 96 + <p> 97 + A virtual table is destroyed using the ordinary <a href="lang_droptable.html">DROP 98 + TABLE</a> statement. There is no DROP VIRTUAL TABLE statement.</p> 99 + <p> 100 + <hr> 101 + </p> 102 + <div id="footer"> 103 + <p> 104 + </p> 105 + <p> 106 + </p> 107 + </div> 108 + </div> 109 + </div> 110 + </body> 111 +</html>
Added Doc/Extra/lang_delete.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>DELETE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">DELETE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + DELETE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">DELETE FROM </font></b>[<b><font color="#2c2cf0"></font></b><i><font 67 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 68 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table-name</font></i><b><font 69 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0">WHERE </font></b><i><font color="#ff3434"> 70 + expr</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 71 + </tr> 72 + </table> 73 + </p> 74 + <p> 75 + The DELETE command is used to remove records from a table. The command consists 76 + of the "DELETE FROM" keywords followed by the 77 + name of the table from which records 78 + are to be removed. 79 + </p> 80 + <p> 81 + Without a WHERE clause, all rows of the table are removed. If a WHERE clause is 82 + supplied, then only those rows that match the expression are removed.</p> 83 + <p> 84 + <hr> 85 + </p> 86 + <div id="footer"> 87 + <p> 88 + </p> 89 + <p> 90 + </p> 91 + </div> 92 + </div> 93 + </div> 94 + </body> 95 +</html>
Added Doc/Extra/lang_detach.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>DETACH</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">DETACH</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + DETACH</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">DETACH </font></b>[<b><font color="#2c2cf0">DATABASE</font></b>]<b><font 67 + color="#2c2cf0"> </font></b><i><font color="#ff3434">database-name</font></i><b><font 68 + color="#2c2cf0"></font></b></td> 69 + </tr> 70 + </table> 71 + </p> 72 + <p> 73 + This statement detaches an additional database connection previously attached using 74 + the <a href="lang_attach.html">ATTACH DATABASE</a> statement. It is possible to have the same database file attached multiple times using different names, and detaching 75 + one connection to a file will leave the others intact.</p> 76 + <p> 77 + This statement will fail if SQLite is in the middle of a transaction.</p> 78 + <p> 79 + <hr> 80 + </p> 81 + <div id="footer"> 82 + <p> 83 + </p> 84 + <p> 85 + </p> 86 + </div> 87 + </div> 88 + </div> 89 + </body> 90 +</html>
Added Doc/Extra/lang_dropindex.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>DROP INDEX</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">DROP INDEX</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + DROP INDEX</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">DROP INDEX </font></b>[<b><font color="#2c2cf0">IF EXISTS</font></b>]<b><font 67 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 68 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 69 + <i><font color="#ff3434">index-name</font></i><b><font color="#2c2cf0"></font></b></td> 70 + </tr> 71 + </table> 72 + </p> 73 + <p> 74 + The DROP INDEX statement removes an index added with the <a href="lang_createindex.html"> 75 + CREATE INDEX</a> statement. The index named is completely removed from the disk. 76 + The only way to recover the index is to reenter the appropriate CREATE INDEX command.</p> 77 + <p> 78 + The DROP INDEX statement does not reduce the size of the database file in the default 79 + mode. Empty space in the database is retained for later INSERTs. To remove free 80 + space in the database, use the <a href="lang_vacuum.html"> 81 + VACUUM</a> command. If 82 + AUTOVACUUM mode is enabled for a database then space will be freed automatically by DROP INDEX.</p> 83 + <p> 84 + <hr> 85 + </p> 86 + <div id="footer"> 87 + <p> 88 + </p> 89 + <p> 90 + </p> 91 + </div> 92 + </div> 93 + </div> 94 + </body> 95 +</html>
Added Doc/Extra/lang_droptable.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>DROP TABLE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">DROP TABLE</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + DROP TABLE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">DROP TABLE </font></b>[<b><font color="#2c2cf0">IF EXISTS</font></b>]<b><font 67 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 68 + color="#2c2cf0"><big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 69 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"></font></b></td> 70 + </tr> 71 + </table> 72 + </p> 73 + <p> 74 + The DROP TABLE statement removes a table added with the <a href="#createtable">CREATE TABLE</a> statement. The 75 + name specified is the table name. It is completely removed 76 + from the database schema and the disk file. The table can not be recovered. All 77 + indices associated with the table are also deleted.</p> 78 + <p> 79 + The DROP TABLE statement does not reduce the size of the database file in the default 80 + mode. Empty space in the database is retained for later INSERTs. To remove free 81 + space in the database, use the <a href="lang_vacuum.html"> 82 + VACUUM</a> command. If 83 + AUTOVACUUM mode is enabled for a database then space will be freed automatically by DROP TABLE.</p> 84 + <p> 85 + The optional IF EXISTS clause suppresses the error that would normally result if the table does not exist.</p> 86 + <p> 87 + <hr> 88 + </p> 89 + <div id="footer"> 90 + <p> 91 + </p> 92 + <p> 93 + </p> 94 + </div> 95 + </div> 96 + </div> 97 + </body> 98 +</html>
Added Doc/Extra/lang_droptrigger.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>DROP TRIGGER</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">DROP TRIGGER</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + DROP TRIGGER</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">DROP TRIGGER </font></b>[<b><font color="#2c2cf0"></font></b><i><font 67 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 68 + color="#2c2cf0"> </font></b><i><font color="#ff3434">trigger-name</font></i><b><font 69 + color="#2c2cf0"></font></b></td> 70 + </tr> 71 + </table> 72 + </p> 73 + <p> 74 + The DROP TRIGGER statement removes a trigger created by the <a href="lang_createtrigger.html"> 75 + CREATE TRIGGER</a> statement. The trigger is deleted from the database schema. 76 + Note that triggers are automatically dropped when the associated table is dropped.</p> 77 + <p> 78 + <hr> 79 + </p> 80 + <div id="footer"> 81 + <p> 82 + </p> 83 + <p> 84 + </p> 85 + </div> 86 + </div> 87 + </div> 88 + </body> 89 +</html>
Added Doc/Extra/lang_dropview.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>DROP VIEW</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">DROP VIEW</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + DROP VIEW</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-command</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">DROP VIEW </font></b><i><font color="#ff3434">view-name</font></i><b><font 67 + color="#2c2cf0"></font></b></td> 68 + </tr> 69 + </table> 70 + </p> 71 + <p> 72 + The DROP VIEW statement removes a view created by the <a href="#createview">CREATE VIEW</a> statement. The 73 + name specified is the view name. It is removed from the 74 + database schema, but no actual data 75 + in the underlying base tables is modified.</p> 76 + <p> 77 + <hr> 78 + </p> 79 + <div id="footer"> 80 + <p> 81 + </p> 82 + <p> 83 + </p> 84 + </div> 85 + </div> 86 + </div> 87 + </body> 88 +</html>
Added Doc/Extra/lang_explain.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>EXPLAIN</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">EXPLAIN</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + EXPLAIN</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">EXPLAIN </font></b><i><font color="#ff3434">sql-statement</font></i><b><font 67 + color="#2c2cf0"></font></b></td> 68 + </tr> 69 + </table> 70 + </p> 71 + <p> 72 + The EXPLAIN command modifier is a non-standard extension. The idea comes from a similar command found in PostgreSQL, but the operation is completely different.</p> 73 + <p> 74 + If the EXPLAIN keyword appears before any 75 + other SQLite SQL command then instead 76 + of actually executing the command, the SQLite library will report back the sequence 77 + of virtual machine instructions it would have used to execute the command had the 78 + EXPLAIN keyword not been present. For additional information about virtual machine 79 + instructions see the <a href="http://www.sqlite.org/arch.html">architecture description</a> 80 + or the documentation on <a href="http://www.sqlite.org/opcode.html">available opcodes</a> 81 + for the virtual machine.</p> 82 + <p> 83 + <hr> 84 + </p> 85 + <div id="footer"> 86 + <p> 87 + </p> 88 + <p> 89 + </p> 90 + </div> 91 + </div> 92 + </div> 93 + </body> 94 +</html>
Added Doc/Extra/lang_expr.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>expression</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">expression</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + expression</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">expr</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">expr</font></i><b><font 67 + color="#2c2cf0"> </font></b><i><font color="#ff3434">binary-op</font></i><b><font 68 + color="#2c2cf0"> </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 69 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 70 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font> 71 + </b>[<b><font color="#2c2cf0">NOT</font></b>]<b><font color="#2c2cf0"> </font></b> 72 + <i><font color="#ff3434">like-op</font></i><b><font color="#2c2cf0"> </font></b> 73 + <i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font></b>[<b><font 74 + color="#2c2cf0">ESCAPE </font></b><i><font color="#ff3434">expr</font></i><b><font 75 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font></b><big>|</big><b><font 76 + color="#2c2cf0"><br /> 77 + </font></b><i><font color="#ff3434">unary-op</font></i><b><font color="#2c2cf0"> </font> 78 + </b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font></b> 79 + <big>|</big><b><font color="#2c2cf0"><br /> 80 + <big>(</big> </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 81 + <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 82 + </font></b><i><font color="#ff3434">column-name</font></i><b><font color="#2c2cf0"> 83 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 84 + </font></b><i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> 85 + <big>.</big> </font></b><i><font color="#ff3434">column-name</font></i><b><font color="#2c2cf0"> 86 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 87 + </font></b><i><font color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> 88 + <big>.</big> </font></b><i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> 89 + <big>.</big> </font></b><i><font color="#ff3434">column-name</font></i><b><font color="#2c2cf0"> 90 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 91 + </font></b><i><font color="#ff3434">literal-value</font></i><b><font color="#2c2cf0"> 92 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 93 + </font></b><i><font color="#ff3434">parameter</font></i><b><font color="#2c2cf0"> 94 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 95 + </font></b><i><font color="#ff3434">function-name</font></i><b><font color="#2c2cf0"> 96 + <big>(</big> </font></b><i><font color="#ff3434">expr-list</font></i><b><font color="#2c2cf0"> 97 + </font></b><big>|</big><b><font color="#2c2cf0"> <big>*</big> <big>)</big> </font> 98 + </b><big>|</big><b><font color="#2c2cf0"><br /> 99 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> ISNULL 100 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 101 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> NOTNULL 102 + </font></b><big>|</big><b><font color="#2c2cf0"><br /> 103 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font> 104 + </b>[<b><font color="#2c2cf0">NOT</font></b>]<b><font color="#2c2cf0"> BETWEEN </font> 105 + </b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> AND </font></b> 106 + <i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font></b><big> 107 + |</big><b><font color="#2c2cf0"><br /> 108 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font> 109 + </b>[<b><font color="#2c2cf0">NOT</font></b>]<b><font color="#2c2cf0"> IN <big>(</big> 110 + </font></b><i><font color="#ff3434">value-list</font></i><b><font color="#2c2cf0"> 111 + <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 112 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font> 113 + </b>[<b><font color="#2c2cf0">NOT</font></b>]<b><font color="#2c2cf0"> IN <big>(</big> 114 + </font></b><i><font color="#ff3434">select-statement</font></i><b><font color="#2c2cf0"> 115 + <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 116 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font> 117 + </b>[<b><font color="#2c2cf0">NOT</font></b>]<b><font color="#2c2cf0"> IN </font></b> 118 + [<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 119 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 120 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> </font></b> 121 + <big>|</big><b><font color="#2c2cf0"><br /> 122 + </font></b>[<b><font color="#2c2cf0">EXISTS</font></b>]<b><font color="#2c2cf0"> <big> 123 + (</big> </font></b><i><font color="#ff3434">select-statement</font></i><b><font color="#2c2cf0"> 124 + <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 125 + CASE </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">expr</font></i><b><font 126 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font></b>(<b><font color="#2c2cf0"> 127 + WHEN </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 128 + THEN </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 129 + </font></b>)+<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0">ELSE </font> 130 + </b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"></font></b>]<b><font 131 + color="#2c2cf0"> END </font></b><big>|</big><b><font color="#2c2cf0"><br /> 132 + CAST <big>(</big> </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> 133 + AS </font></b><i><font color="#ff3434">type</font></i><b><font color="#2c2cf0"> <big> 134 + )</big></font></b></td> 135 + </tr> 136 + <tr> 137 + <td align="right" valign="top"> 138 + <i><font color="#ff3434">like-op</font></i> ::=</td> 139 + <td> 140 + <b><font color="#2c2cf0">LIKE </font></b><big>|</big><b><font color="#2c2cf0"> GLOB 141 + </font></b><big>|</big><b><font color="#2c2cf0"> REGEXP </font></b><big>|</big><b><font 142 + color="#2c2cf0"> MATCH</font></b></td> 143 + </tr> 144 + </table> 145 + </p> 146 + <p> 147 + This section is different from the others. Most other sections of this document 148 + talks about a particular SQL command. This section does not talk about a standalone 149 + command but about "expressions" which are subcomponents of most other commands.</p> 150 + <p> 151 + SQLite understands the following binary operators, in order from highest to lowest 152 + precedence:</p> 153 + <blockquote> 154 + <pre> 155 +<font color="#2c2cf0"><big>|| * / % + - << >> & | < <= > 156 + >= = == != <> </big>IN AND OR</font> 157 +</pre> 158 + </blockquote> 159 + <p> 160 + Supported unary operators are these:</p> 161 + <blockquote> 162 + <pre> 163 +<font color="#2c2cf0"><big>- + ! ~ NOT</big></font> 164 +</pre> 165 + </blockquote> 166 + <p> 167 + The unary operator [Operator +] is a no-op. It can be applied to strings, numbers, 168 + or blobs and it always gives as its result the value of the operand.</p> 169 + <p> 170 + Note that there are two variations of the equals and not equals operators. Equals 171 + can be either <font color="#2c2cf0"><big>=</big></font> or <font color="#2c2cf0"><big> 172 + ==</big></font>. The non-equals operator can be either <font color="#2c2cf0"><big> 173 + !=</big></font> or <font color="#2c2cf0"><big><></big></font>. The <font color="#2c2cf0"> 174 + <big>||</big></font> operator is "concatenate" - it joins together the two 175 + strings of its operands. The operator <font color="#2c2cf0"><big>%</big></font> 176 + outputs the remainder of its left operand modulo its right operand.</p> 177 + <p> 178 + The result of any binary operator is a numeric value, except for the <font color="#2c2cf0"> 179 + <big>||</big></font> concatenation operator which gives a string result.</p> 180 + <a name="literal_value"></a> 181 + <p> 182 + A literal value is an integer number or a floating point number. Scientific notation 183 + is supported. The "." character is always used as the decimal point even if the 184 + locale setting specifies "," for this role - the use of "," for the decimal point 185 + would result in syntactic ambiguity. A string constant is formed by enclosing the 186 + string in single quotes ('). A single quote within the string can be encoded by 187 + putting two single quotes in a row - as in Pascal. C-style escapes using the backslash 188 + character are not supported because they are not standard SQL. BLOB literals are 189 + string literals containing hexadecimal data and preceded by a single "x" or "X" 190 + character. For example:</p> 191 + <blockquote> 192 + <pre> 193 +X'53514697465' 194 +</pre> 195 + </blockquote> 196 + <p> 197 + A literal value can also be the token "NULL". 198 + </p> 199 + <p> 200 + A parameter specifies a placeholder in the expression for a literal value that is 201 + filled in at runtime using the <a href="capi3ref.html#sqlite3_bind_int">sqlite3_bind</a> 202 + API. Parameters can take several forms: 203 + </p> 204 + <p> 205 + <table> 206 + <tr> 207 + <td align="right" valign="top"> 208 + <b>?</b><i>NNN</i></td> 209 + <td width="20"> 210 + </td> 211 + <td> 212 + A question mark followed by a number <i>NNN</i> holds a spot for the NNN-th parameter. 213 + NNN must be between 1 and 999.</td> 214 + </tr> 215 + <tr> 216 + <td align="right" valign="top"> 217 + <b>?</b></td> 218 + <td width="20"> 219 + </td> 220 + <td> 221 + A question mark that is not followed by a number holds a spot for the next unused 222 + parameter.</td> 223 + </tr> 224 + <tr> 225 + <td align="right" valign="top"> 226 + <b>:</b><i>AAAA</i></td> 227 + <td width="20"> 228 + </td> 229 + <td> 230 + A colon followed by an identifier name holds a spot for a named parameter with the 231 + name AAAA. Named parameters are also numbered. The number assigned is the next unused 232 + number. To avoid confusion, it is best to avoid mixing named and numbered parameters.</td> 233 + </tr> 234 + <tr> 235 + <td align="right" valign="top"> 236 + <b>@</b><i>AAAA</i></td> 237 + <td width="20"> 238 + </td> 239 + <td> 240 + An "at" sign works exactly like a colon.</td> 241 + </tr> 242 + <tr> 243 + <td align="right" valign="top"> 244 + <b>$</b><i>AAAA</i></td> 245 + <td width="20"> 246 + </td> 247 + <td> 248 + A dollar-sign followed by an identifier name also holds a spot for a named parameter 249 + with the name AAAA. The identifier name in this case can include one or more occurances 250 + of "::" and a suffix enclosed in "(...)" containing any text at all. This syntax 251 + is the form of a variable name in the Tcl programming language.</td> 252 + </tr> 253 + </table> 254 + </p> 255 + <blockquote> 256 + </blockquote> 257 + <p> 258 + Parameters that are not assigned values using <a href="capi3ref.html#sqlite3_bind_int"> 259 + sqlite3_bind</a> are treated as NULL.</p> 260 + <a name="like"></a> 261 + <p> 262 + The LIKE operator does a pattern matching comparison. The operand to the right contains 263 + the pattern, the left hand operand contains the string to match against the pattern. 264 + A percent symbol <font color="#2c2cf0"><big>%</big></font> in the pattern matches 265 + any sequence of zero or more characters in the string. An underscore <font color="#2c2cf0"> 266 + <big>_</big></font> in the pattern matches any single character in the string. 267 + Any other character matches itself or it's lower/upper case equivalent (i.e. case-insensitive 268 + matching). (A bug: SQLite only understands upper/lower case for 7-bit Latin characters. 269 + Hence the LIKE operator is case sensitive for 8-bit iso8859 characters or UTF-8 270 + characters. For example, the expression <b>'a' LIKE 'A'</b> is TRUE but <b>'æ' LIKE 271 + 'Æ'</b> is FALSE.).</p> 272 + <p> 273 + If the optional ESCAPE clause is present, then the expression following the ESCAPE 274 + keyword must evaluate to a string consisting of a single character. This character 275 + may be used in the LIKE pattern to include literal percent or underscore characters. 276 + The escape character followed by a percent symbol, underscore or itself matches 277 + a literal percent symbol, underscore or escape character in the string, respectively. 278 + The infix LIKE operator is implemented by calling the user function <a href="#likeFunc"> 279 + like(<i>X</i>,<i>Y</i>)</a>.</p> 280 + <p> 281 + The LIKE operator is not case sensitive and will match upper case characters on 282 + one side against lower case characters on the other. (A bug: SQLite only understands 283 + upper/lower case for 7-bit Latin characters. Hence the LIKE operator is case sensitive 284 + for 8-bit iso8859 characters or UTF-8 characters. For example, the expression <b>'a' 285 + LIKE 'A'</b> is TRUE but <b>'æ' LIKE 'Æ'</b> is FALSE.). 286 + </p> 287 + <p> 288 + </p> 289 + <p> 290 + The infix LIKE operator is implemented by calling the user function <a href="#likeFunc"> 291 + like(<i>X</i>,<i>Y</i>)</a>. If an ESCAPE clause is present, it adds a third parameter 292 + to the function call. If the functionality of LIKE can be overridden by defining 293 + an alternative implementation of the like() SQL function.</p> 294 + <p> 295 + </p> 296 + <a name="glob"></a> 297 + <p> 298 + The GLOB operator is similar to LIKE but uses the Unix file globbing syntax for 299 + its wildcards. Also, GLOB is case sensitive, unlike LIKE. Both GLOB and LIKE may 300 + be preceded by the NOT keyword to invert the sense of the test. The infix GLOB operator 301 + is implemented by calling the user function <a href="#globFunc">glob(<i>X</i>,<i>Y</i>)</a> 302 + and can be modified by overriding that function.</p> 303 + <a name="regexp"></a> 304 + <p> 305 + The REGEXP operator is a special syntax for the regexp() user function. No regexp() 306 + user function is defined by default and so use of the REGEXP operator will normally 307 + result in an error message. If a user-defined function named "regexp" is added at 308 + run-time, that function will be called in order to implement the REGEXP operator.</p> 309 + <a name="match"></a> 310 + <p> 311 + The MATCH operator is a special syntax for the match() user function. The default 312 + match() function implementation raises and exception and is not really useful for 313 + anything. But extensions can override the match() function with more helpful logic.</p> 314 + <p> 315 + A column name can be any of the names defined in the CREATE TABLE statement or one 316 + of the following special identifiers: "<b>ROWID</b>", "<b>OID</b>", or "<b>_ROWID_</b>". 317 + These special identifiers all describe the unique random integer key (the "row key") 318 + associated with every row of every table. The special identifiers only refer to 319 + the row key if the CREATE TABLE statement does not define a real column with the 320 + same name. Row keys act like read-only columns. A row key can be used anywhere a 321 + regular column can be used, except that you cannot change the value of a row key 322 + in an UPDATE or INSERT statement. "SELECT * ..." does not return the row key.</p> 323 + <p> 324 + SELECT statements can appear in expressions as either the right-hand operand of 325 + the IN operator, as a scalar quantity, or as the operand of an EXISTS operator. 326 + As a scalar quantity or the operand of an IN operator, the SELECT should have only 327 + a single column in its result. Compound SELECTs (connected with keywords like UNION 328 + or EXCEPT) are allowed. With the EXISTS operator, the columns in the result set 329 + of the SELECT are ignored and the expression returns TRUE if one or more rows exist 330 + and FALSE if the result set is empty. If no terms in the SELECT expression refer 331 + to value in the containing query, then the expression is evaluated once prior to 332 + any other processing and the result is reused as necessary. If the SELECT expression 333 + does contain variables from the outer query, then the SELECT is reevaluated every 334 + time it is needed.</p> 335 + <p> 336 + When a SELECT is the right operand of the IN operator, the IN operator returns TRUE 337 + if the result of the left operand is any of the values generated by the select. 338 + The IN operator may be preceded by the NOT keyword to invert the sense of the test.</p> 339 + <p> 340 + When a SELECT appears within an expression but is not the right operand of an IN 341 + operator, then the first row of the result of the SELECT becomes the value used 342 + in the expression. If the SELECT yields more than one result row, all rows after the first are ignored. If the SELECT yields no rows, then the value of the SELECT 343 + is NULL.</p> 344 + <p> 345 + A CAST expression changes the datatype of the 346 + <expr> 347 +</expr> 348 + into the type specified by <type>. <type> can be any non-empty type 349 + name that is valid for the type in a column definition of a CREATE TABLE statement.</p> 350 + <p> 351 + Both simple and aggregate functions are supported. A simple function can be used 352 + in any expression. Simple functions return a result immediately based on their inputs. 353 + Aggregate functions may only be used in a SELECT statement. Aggregate functions 354 + compute their result across all rows of the result set.</p> 355 + <p> 356 + <a name="corefunctions"></a><b>Core Functions</b> 357 + </p> 358 + <p> 359 + The core functions shown below are available by default. Additional functions may 360 + be written in C and added to the database engine using the <a href="capi3ref.html#cfunc"> 361 + sqlite3_create_function()</a> API.</p> 362 + <p> 363 + <table border="0" cellpadding="10"> 364 + <tr> 365 + <td align="right" valign="top" width="120"> 366 + abs(<i>X</i>)</td> 367 + <td valign="top"> 368 + Return the absolute value of argument <i>X</i>.</td> 369 + </tr> 370 + <tr> 371 + <td align="right" valign="top"> 372 + coalesce(<i>X</i>,<i>Y</i>,...)</td> 373 + <td valign="top"> 374 + Return a copy of the first non-NULL argument. If all arguments are NULL then NULL 375 + is returned. There must be at least 2 arguments.</td> 376 + </tr> 377 + <tr> 378 + <a name="globFunc"></a> 379 + <td align="right" valign="top"> 380 + glob(<i>X</i>,<i>Y</i>)</td> 381 + <td valign="top"> 382 + This function is used to implement the "<b>X GLOB Y</b>" syntax of SQLite. The <a 383 + href="capi3ref.html#sqlite3_create_function">sqlite3_create_function()</a> interface 384 + can be used to override this function and thereby change the operation of the <a 385 + href="#globFunc">GLOB</a> operator.</td> 386 + </tr> 387 + <tr> 388 + <td align="right" valign="top"> 389 + ifnull(<i>X</i>,<i>Y</i>)</td> 390 + <td valign="top"> 391 + Return a copy of the first non-NULL argument. If both arguments are NULL then NULL 392 + is returned. This behaves the same as <b>coalesce()</b> above.</td> 393 + </tr> 394 + <tr> 395 + <td align="right" valign="top"> 396 + last_insert_rowid()</td> 397 + <td valign="top"> 398 + Return the ROWID of the last row insert from this connection to the database. This 399 + is the same value that would be returned from the <b>sqlite_last_insert_rowid()</b> 400 + API function.</td> 401 + </tr> 402 + <tr> 403 + <td align="right" valign="top"> 404 + length(<i>X</i>)</td> 405 + <td valign="top"> 406 + Return the string length of <i>X</i> in characters. If SQLite is configured to support 407 + UTF-8, then the number of UTF-8 characters is returned, not the number of bytes.</td> 408 + </tr> 409 + <tr> 410 + <a name="likeFunc"></a> 411 + <td align="right" valign="top"> 412 + like(<i>X</i>,<i>Y</i> [,<i>Z</i>])</td> 413 + <td valign="top"> 414 + This function is used to implement the "<b>X LIKE Y [ESCAPE Z]</b>" syntax of SQL. 415 + If the optional ESCAPE clause is present, then the user-function is invoked with 416 + three arguments. Otherwise, it is invoked with two arguments only. The <a href="capi3ref.html#sqlite3_create_function"> 417 + sqlite_create_function()</a> interface can be used to override this function and 418 + thereby change the operation of the <a href="#like">LIKE</a> operator. When doing 419 + this, it may be important to override both the two and three argument versions of 420 + the like() function. Otherwise, different code may be called to implement the LIKE 421 + operator depending on whether or not an ESCAPE clause was specified.</td> 422 + </tr> 423 + <tr> 424 + <td align="right" valign="top"> 425 + load_extension(<i>X</i>)<br /> 426 + load_extension(<i>X</i>,<i>Y</i>)</td> 427 + <td valign="top"> 428 + Load SQLite extensions out of the shared library file named <i>X</i> using the entry 429 + point <i>Y</i>. The result is a NULL. If <i>Y</i> is omitted then the default entry 430 + point of <b>sqlite3_extension_init</b> is used. This function raises an exception 431 + if the extension fails to load or initialize correctly. 432 + </td> 433 + </tr> 434 + <tr> 435 + <td align="right" valign="top"> 436 + lower(<i>X</i>)</td> 437 + <td valign="top"> 438 + Return a copy of string <i>X</i> will all characters converted to lower case. The 439 + C library <b>tolower()</b> routine is used for the conversion, which means that 440 + this function might not work correctly on UTF-8 characters.</td> 441 + </tr> 442 + <tr> 443 + <td align="right" valign="top"> 444 + max(<i>X</i>,<i>Y</i>,...)</td> 445 + <td valign="top"> 446 + Return the argument with the maximum value. Arguments may be strings in addition 447 + to numbers. The maximum value is determined by the usual sort order. Note that <b> 448 + max()</b> is a simple function when it has 2 or more arguments but converts to 449 + an aggregate function if given only a single argument.</td> 450 + </tr> 451 + <tr> 452 + <td align="right" valign="top"> 453 + min(<i>X</i>,<i>Y</i>,...)</td> 454 + <td valign="top"> 455 + Return the argument with the minimum value. Arguments may be strings in addition 456 + to numbers. The minimum value is determined by the usual sort order. Note that <b> 457 + min()</b> is a simple function when it has 2 or more arguments but converts to 458 + an aggregate function if given only a single argument.</td> 459 + </tr> 460 + <tr> 461 + <td align="right" valign="top"> 462 + nullif(<i>X</i>,<i>Y</i>)</td> 463 + <td valign="top"> 464 + Return the first argument if the arguments are different, otherwise return NULL.</td> 465 + </tr> 466 + <tr> 467 + <td align="right" valign="top"> 468 + quote(<i>X</i>)</td> 469 + <td valign="top"> 470 + This routine returns a string which is the value of its argument suitable for inclusion 471 + into another SQL statement. Strings are surrounded by single-quotes with escapes 472 + on interior quotes as needed. BLOBs are encoded as hexadecimal literals. The current 473 + implementation of 474 + VACUUM uses this function. The function is also useful when writing 475 + triggers to implement undo/redo functionality. 476 + </td> 477 + </tr> 478 + <tr> 479 + <td align="right" valign="top"> 480 + random(*)</td> 481 + <td valign="top"> 482 + Return a pseudo-random integer between -9223372036854775808 and +9223372036854775807.</td> 483 + </tr> 484 + <tr> 485 + <td align="right" valign="top"> 486 + round(<i>X</i>)<br /> 487 + round(<i>X</i>,<i>Y</i>)</td> 488 + <td valign="top"> 489 + Round off the number <i>X</i> to <i>Y</i> digits to the right of the decimal point. 490 + If the <i>Y</i> argument is omitted, 0 is assumed.</td> 491 + </tr> 492 + <tr> 493 + <td align="right" valign="top"> 494 + soundex(<i>X</i>)</td> 495 + <td valign="top"> 496 + Compute the soundex encoding of the string <i>X</i>. The string "?000" is returned 497 + if the argument is NULL. This function is omitted from SQLite by default. It is 498 + only available the -DSQLITE_SOUNDEX=1 compiler option is used when SQLite is built.</td> 499 + </tr> 500 + <tr> 501 + <td align="right" valign="top"> 502 + sqlite_version(*)</td> 503 + <td valign="top"> 504 + Return the version string for the SQLite library that is running. Example: "2.8.0"</td> 505 + </tr> 506 + <tr> 507 + <td align="right" valign="top"> 508 + substr(<i>X</i>,<i>Y</i>,<i>Z</i>)</td> 509 + <td valign="top"> 510 + Return a substring of input string <i>X</i> that begins with the <i>Y</i>-th character 511 + and which is <i>Z</i> characters long. The left-most character of <i>X</i> is number 512 + 1. If <i>Y</i> is negative the the first character of the substring is found by 513 + counting from the right rather than the left. If SQLite is configured to support 514 + UTF-8, then characters indices refer to actual UTF-8 characters, not bytes.</td> 515 + </tr> 516 + <tr> 517 + <td align="right" valign="top"> 518 + typeof(<i>X</i>)</td> 519 + <td valign="top"> 520 + Return the type of the expression <i>X</i>. The only return values are "null", "integer", 521 + "real", "text", and "blob". 522 + SQLite's type handling is explained in <a href="http://www.sqlite.org/datatype3.html"> 523 + Datatypes in SQLite Version 3</a>.</td> 524 + </tr> 525 + <tr> 526 + <td align="right" valign="top"> 527 + upper(<i>X</i>)</td> 528 + <td valign="top"> 529 + Return a copy of input string <i>X</i> converted to all upper-case letters. The 530 + implementation of this function uses the C library routine <b>toupper()</b> which 531 + means it may not work correctly on UTF-8 strings.</td> 532 + </tr> 533 + </table> 534 + <b>Date And Time Functions</b> 535 + </p> 536 + <p> 537 + Date and time functions are documented in the <a href="http://www.sqlite.org/cvstrac/wiki?p=DateAndTimeFunctions"> 538 + SQLite Wiki</a>.</p> 539 + <p> 540 + <a name="aggregatefunctions"></a><b>Aggregate Functions</b> 541 + </p> 542 + <p> 543 + The aggregate functions shown below are available by default. Additional aggregate 544 + functions written in C may be added using the <a href="capi3ref.html#sqlite3_create_function"> 545 + sqlite3_create_function()</a> API.</p> 546 + <p> 547 + In any aggregate function that takes a single argument, that argument can be preceeded 548 + by the keyword DISTINCT. In such cases, duplicate elements are filtered before being 549 + passed into the aggregate function. For example, the function "count(distinct X)" 550 + will return the number of distinct values of column X instead of the total number 551 + of non-null values in column X. 552 + </p> 553 + <p> 554 + <table border="0" cellpadding="10"> 555 + <tr> 556 + <td align="right" valign="top" width="120"> 557 + avg(<i>X</i>)</td> 558 + <td valign="top"> 559 + Return the average value of all non-NULL <i>X</i> within a group. String and BLOB 560 + values that do not look like numbers are interpreted as 0. The result of avg() is 561 + always a floating point value even if all inputs are integers. 562 + <p> 563 + </p> 564 + </td> 565 + </tr> 566 + <tr> 567 + <td align="right" valign="top"> 568 + count(<i>X</i>)<br /> 569 + count(*)</td> 570 + <td valign="top"> 571 + The first form return a count of the number of times that <i>X</i> is not NULL in 572 + a group. The second form (with no argument) returns the total number of rows in 573 + the group.</td> 574 + </tr> 575 + <tr> 576 + <td align="right" valign="top"> 577 + max(<i>X</i>)</td> 578 + <td valign="top"> 579 + Return the maximum value of all values in the group. The usual sort order is used 580 + to determine the maximum.</td> 581 + </tr> 582 + <tr> 583 + <td align="right" valign="top"> 584 + min(<i>X</i>)</td> 585 + <td valign="top"> 586 + Return the minimum non-NULL value of all values in the group. The usual sort order 587 + is used to determine the minimum. NULL is only returned if all values in the group 588 + are NULL.</td> 589 + </tr> 590 + <tr> 591 + <td align="right" valign="top"> 592 + sum(<i>X</i>)<br /> 593 + total(<i>X</i>)</td> 594 + <td valign="top"> 595 + Return the numeric sum of all non-NULL values in the group. If there are no non-NULL 596 + input rows then sum() returns NULL but total() returns 0.0. NULL is not normally 597 + a helpful result for the sum of no rows but the SQL standard requires it and most 598 + other SQL database engines implement sum() that way so SQLite does it in the same 599 + way in order to be compatible. The non-standard total() function is provided as 600 + a convenient way to work around this design problem in the SQL language. 601 + <p> 602 + </p> 603 + <p> 604 + The result of total() is always a floating point value. The result of sum() is an 605 + integer value if all non-NULL inputs are integers. If any input to sum() is neither 606 + an integer or a NULL then sum() returns a floating point value which might be an 607 + approximation to the true sum.</p> 608 + <p> 609 + Sum() will throw an "integer overflow" exception if all inputs are integers or NULL 610 + and an integer overflow occurs at any point during the computation. Total() never 611 + throws an exception.</p> 612 + </td> 613 + </tr> 614 + </table> 615 + </p> 616 + <p> 617 + <hr> 618 + </p> 619 + <div id="footer"> 620 + <p> 621 + </p> 622 + <p> 623 + </p> 624 + </div> 625 + </div> 626 + </div> 627 + </body> 628 +</html>
Added Doc/Extra/lang_insert.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>INSERT</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">INSERT</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + INSERT</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">INSERT </font></b>[<b><font color="#2c2cf0">OR </font></b> 67 + <i><font color="#ff3434">conflict-algorithm</font></i><b><font color="#2c2cf0"></font></b>]<b><font 68 + color="#2c2cf0"> INTO </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 69 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 70 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> </font></b> 71 + [<b><font color="#2c2cf0"><big>(</big></font></b><i><font color="#ff3434">column-list</font></i><b><font 72 + color="#2c2cf0"><big>)</big></font></b>]<b><font color="#2c2cf0"> VALUES<big>(</big></font></b><i><font 73 + color="#ff3434">value-list</font></i><b><font color="#2c2cf0"><big>)</big> </font> 74 + </b><big>|</big><b><font color="#2c2cf0"><br /> 75 + INSERT </font></b>[<b><font color="#2c2cf0">OR </font></b><i><font color="#ff3434"> 76 + conflict-algorithm</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> 77 + INTO </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 78 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 79 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> </font></b> 80 + [<b><font color="#2c2cf0"><big>(</big></font></b><i><font color="#ff3434">column-list</font></i><b><font 81 + color="#2c2cf0"><big>)</big></font></b>]<b><font color="#2c2cf0"> </font></b><i><font 82 + color="#ff3434">select-statement</font></i><b><font color="#2c2cf0"></font></b></td> 83 + </tr> 84 + </table> 85 + </p> 86 + <p> 87 + The INSERT statement comes in two basic forms. The first form (with the "VALUES" 88 + keyword) creates a single new row in an existing table. If no column-list is specified 89 + then the number of values must be the same as the number of columns in the table. 90 + If a column-list is specified, then the number of values must match the number of 91 + specified columns. Columns of the table that do not appear in the column list are 92 + filled with the default value, or with NULL if not default value is specified. 93 + </p> 94 + <p> 95 + The second form of the INSERT statement takes it data 96 + from a SELECT statement. The 97 + number of columns in the result of the SELECT must exactly match the number of columns 98 + in the table if no column list is specified, or it must match the number of columns 99 + name in the column list. A new entry is made in the table for every row of the SELECT 100 + result. The SELECT may be simple or compound. If the SELECT statement has an ORDER 101 + BY clause, the ORDER BY is ignored.</p> 102 + <p> 103 + The optional conflict-clause allows the specification of an alternative constraint conflict resolution algorithm to use during this one command. See the section titled 104 + <a href="lang_conflict.html">ON CONFLICT</a> for additional information. For compatibility 105 + with MySQL, the parser allows the use of the single keyword <a href="lang_replace.html"> 106 + REPLACE</a> as an alias for "INSERT OR REPLACE". 107 + </p> 108 + <p> 109 + <hr> 110 + </p> 111 + <div id="footer"> 112 + <p> 113 + </p> 114 + <p> 115 + </p> 116 + </div> 117 + </div> 118 + </div> 119 + </body> 120 +</html>
Added Doc/Extra/lang_reindex.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>REINDEX</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + REINDEX </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + REINDEX</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">REINDEX </font></b><i><font color="#ff3434">collation 67 + name</font></i><b><font 68 + color="#2c2cf0"></font></b></td> 69 + </tr> 70 + </table> 71 + <table cellpadding="10"> 72 + <tr> 73 + <td align="right" valign="top"> 74 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 75 + <td> 76 + <b><font color="#2c2cf0">REINDEX </font></b>[<b><font color="#2c2cf0"></font></b><i><font 77 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 78 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table/index-name</font></i><b><font 79 + color="#2c2cf0"></font></b></td> 80 + </tr> 81 + </table> 82 + </p> 83 + <p> 84 + The REINDEX command is used to delete and recreate indices from scratch. This is 85 + useful when the definition of a collation sequence has changed. 86 + </p> 87 + <p> 88 + In the first form, all indices in all attached databases that use the named collation 89 + sequence are recreated. In the second form, if <i>[database-name.]table/index-name</i> 90 + identifies a table, then all indices associated with the table are rebuilt. If an 91 + index is identified, then only this specific index is deleted and recreated. 92 + </p> 93 + <p> 94 + If no <i>database-name</i> is specified and there exists both a table or index and 95 + a collation sequence of the specified name, then indices associated with the collation 96 + sequence only are reconstructed. This ambiguity may be dispelled by always specifying 97 + a <i>database-name</i> when reindexing a specific table or index. 98 + </p> 99 + <p> 100 + <hr> 101 + </p> 102 + <div id="footer"> 103 + <p> 104 + </p> 105 + <p> 106 + </p> 107 + </div> 108 + </div> 109 + </div> 110 + </body> 111 +</html>
Added Doc/Extra/lang_replace.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>REPLACE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + REPLACE </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + REPLACE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">REPLACE INTO </font></b>[<b><font color="#2c2cf0"></font></b><i><font 67 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 68 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table-name</font></i><b><font 69 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"><big>(</big> </font></b> 70 + <i><font color="#ff3434">column-list</font></i><b><font color="#2c2cf0"> <big>)</big></font></b>]<b><font 71 + color="#2c2cf0"> VALUES <big>(</big> </font></b><i><font color="#ff3434">value-list</font></i><b><font 72 + color="#2c2cf0"> <big>)</big> </font></b><big>|</big><b><font color="#2c2cf0"><br /> 73 + REPLACE INTO </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">database-name</font></i><b><font 74 + color="#2c2cf0"> <big>.</big></font></b>]<b><font color="#2c2cf0"> </font></b> 75 + <i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> </font></b> 76 + [<b><font color="#2c2cf0"><big>(</big> </font></b><i><font color="#ff3434">column-list</font></i><b><font 77 + color="#2c2cf0"> <big>)</big></font></b>]<b><font color="#2c2cf0"> </font></b> 78 + <i><font color="#ff3434">select-statement</font></i><b><font color="#2c2cf0"></font></b></td> 79 + </tr> 80 + </table> 81 + </p> 82 + <p> 83 + The REPLACE command is an alias for the "INSERT OR REPLACE" variant of the <a href="lang_insert.html"> 84 + INSERT</a> command. This alias is provided for compatibility with MySQL. See the 85 + <a href="lang_insert.html">INSERT</a> command documentation for additional information.</p> 86 + <p> 87 + <hr> 88 + </p> 89 + <div id="footer"> 90 + <p> 91 + </p> 92 + <p> 93 + </p> 94 + </div> 95 + </div> 96 + </div> 97 + </body> 98 +</html>
Added Doc/Extra/lang_select.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>SELECT</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + SELECT </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + SELECT</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">SELECT </font></b>[<b><font color="#2c2cf0">ALL </font></b> 67 + <big>|</big><b><font color="#2c2cf0"> DISTINCT</font></b>]<b><font color="#2c2cf0"> 68 + </font></b><i><font color="#ff3434">result</font></i><b><font color="#2c2cf0"> </font> 69 + </b>[<b><font color="#2c2cf0">FROM </font></b><i><font color="#ff3434">table-list</font></i><b><font 70 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"><br /> 71 + </font></b>[<b><font color="#2c2cf0">WHERE </font></b><i><font color="#ff3434">expr</font></i><b><font 72 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"><br /> 73 + </font></b>[<b><font color="#2c2cf0">GROUP BY </font></b><i><font color="#ff3434"> 74 + expr-list</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"><br /> 75 + </font></b>[<b><font color="#2c2cf0">HAVING </font></b><i><font color="#ff3434">expr</font></i><b><font 76 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"><br /> 77 + </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">compound-op</font></i><b><font 78 + color="#2c2cf0"> </font></b><i><font color="#ff3434">select</font></i><b><font color="#2c2cf0"></font></b>]<b><font 79 + color="#2c2cf0"></font></b><big>*</big><b><font color="#2c2cf0"><br /> 80 + </font></b>[<b><font color="#2c2cf0">ORDER BY </font></b><i><font color="#ff3434"> 81 + sort-expr-list</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"><br /> 82 + </font></b>[<b><font color="#2c2cf0">LIMIT </font></b><i><font color="#ff3434">integer</font></i><b><font 83 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b>(<b><font color="#2c2cf0"> 84 + OFFSET </font></b><big>|</big><b><font color="#2c2cf0"> <big>,</big> </font></b> 85 + )<b><font color="#2c2cf0"> </font></b><i><font color="#ff3434">integer</font></i><b><font 86 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 87 + </tr> 88 + <tr> 89 + <td align="right" valign="top"> 90 + <i><font color="#ff3434">result</font></i> ::=</td> 91 + <td> 92 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">result-column</font></i><b><font 93 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"><big>,</big> </font></b> 94 + <i><font color="#ff3434">result-column</font></i><b><font color="#2c2cf0"></font></b>]<b><font 95 + color="#2c2cf0"></font></b><big>*</big><b><font color="#2c2cf0"></font></b></td> 96 + </tr> 97 + <tr> 98 + <td align="right" valign="top"> 99 + <i><font color="#ff3434">result-column</font></i> ::=</td> 100 + <td> 101 + <b><font color="#2c2cf0"><big>*</big> </font></b><big>|</big><b><font color="#2c2cf0"> 102 + </font></b><i><font color="#ff3434">table-name</font></i><b><font color="#2c2cf0"> 103 + <big>.</big> <big>*</big> </font></b><big>|</big><b><font color="#2c2cf0"> </font> 104 + </b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font></b> 105 + [<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0">AS</font></b>]<b><font 106 + color="#2c2cf0"> </font></b><i><font color="#ff3434">string</font></i><b><font color="#2c2cf0"> 107 + </font></b>]<b><font color="#2c2cf0"></font></b></td> 108 + </tr> 109 + <tr> 110 + <td align="right" valign="top"> 111 + <i><font color="#ff3434">table-list</font></i> ::=</td> 112 + <td> 113 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">table</font></i><b><font 114 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">join-op</font></i><b><font 115 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table</font></i><b><font color="#2c2cf0"> 116 + </font></b><i><font color="#ff3434">join-args</font></i><b><font color="#2c2cf0"></font></b>]<b><font 117 + color="#2c2cf0"></font></b><big>*</big><b><font color="#2c2cf0"></font></b></td> 118 + </tr> 119 + <tr> 120 + <td align="right" valign="top"> 121 + <i><font color="#ff3434">table</font></i> ::=</td> 122 + <td> 123 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">table-name</font></i><b><font 124 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0">AS </font></b><i><font color="#ff3434"> 125 + alias</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font> 126 + </b><big>|</big><b><font color="#2c2cf0"><br /> 127 + <big>(</big> </font></b><i><font color="#ff3434">select</font></i><b><font color="#2c2cf0"> 128 + <big>)</big> </font></b>[<b><font color="#2c2cf0">AS </font></b><i><font color="#ff3434"> 129 + alias</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 130 + </tr> 131 + <tr> 132 + <td align="right" valign="top"> 133 + <i><font color="#ff3434">join-op</font></i> ::=</td> 134 + <td> 135 + <b><font color="#2c2cf0"><big>,</big> </font></b><big>|</big><b><font color="#2c2cf0"> 136 + </font></b>[<b><font color="#2c2cf0">NATURAL</font></b>]<b><font color="#2c2cf0"> 137 + </font></b>[<b><font color="#2c2cf0">LEFT </font></b><big>|</big><b><font color="#2c2cf0"> 138 + RIGHT </font></b><big>|</big><b><font color="#2c2cf0"> FULL</font></b>]<b><font color="#2c2cf0"> 139 + </font></b>[<b><font color="#2c2cf0">OUTER </font></b><big>|</big><b><font color="#2c2cf0"> 140 + INNER </font></b><big>|</big><b><font color="#2c2cf0"> CROSS</font></b>]<b><font 141 + color="#2c2cf0"> JOIN</font></b></td> 142 + </tr> 143 + <tr> 144 + <td align="right" valign="top"> 145 + <i><font color="#ff3434">join-args</font></i> ::=</td> 146 + <td> 147 + <b><font color="#2c2cf0"></font></b>[<b><font color="#2c2cf0">ON </font></b><i><font 148 + color="#ff3434">expr</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> 149 + </font></b>[<b><font color="#2c2cf0">USING <big>(</big> </font></b><i><font color="#ff3434"> 150 + id-list</font></i><b><font color="#2c2cf0"> <big>)</big></font></b>]<b><font color="#2c2cf0"></font></b></td> 151 + </tr> 152 + <tr> 153 + <td align="right" valign="top"> 154 + <i><font color="#ff3434">sort-expr-list</font></i> ::=</td> 155 + <td> 156 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">expr</font></i><b><font 157 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">sort-order</font></i><b><font 158 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"><big>,</big> 159 + </font></b><i><font color="#ff3434">expr</font></i><b><font color="#2c2cf0"> </font> 160 + </b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">sort-order</font></i><b><font 161 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b><big>*</big><b><font 162 + color="#2c2cf0"></font></b></td> 163 + </tr> 164 + <tr> 165 + <td align="right" valign="top"> 166 + <i><font color="#ff3434">sort-order</font></i> ::=</td> 167 + <td> 168 + <b><font color="#2c2cf0"></font></b>[<b><font color="#2c2cf0"> COLLATE </font></b> 169 + <i><font color="#ff3434">collation-name</font></i><b><font color="#2c2cf0"> </font> 170 + </b>]<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"> ASC </font></b> 171 + <big>|</big><b><font color="#2c2cf0"> DESC </font></b>]<b><font color="#2c2cf0"></font></b></td> 172 + </tr> 173 + <tr> 174 + <td align="right" valign="top"> 175 + <i><font color="#ff3434">compound_op</font></i> ::=</td> 176 + <td> 177 + <b><font color="#2c2cf0">UNION </font></b><big>|</big><b><font color="#2c2cf0"> UNION 178 + ALL </font></b><big>|</big><b><font color="#2c2cf0"> INTERSECT </font></b><big>|</big><b><font 179 + color="#2c2cf0"> EXCEPT</font></b></td> 180 + </tr> 181 + </table> 182 + </p> 183 + <p> 184 + The SELECT statement is used to query the database. The result of a SELECT is zero 185 + or more rows of data where each row has a fixed number of columns. The number of 186 + columns in the result is specified by the expression list in between the SELECT 187 + and FROM keywords. Any arbitrary expression can be used as a result. If a result 188 + expression is <font color="#2c2cf0"><big>*</big></font> then all columns of all 189 + tables are substituted for that one expression. If the expression is the name of 190 + a table followed by <font color="#2c2cf0"><big>.*</big></font> then the result is 191 + all columns in that one table.</p> 192 + <p> 193 + The DISTINCT keyword causes a subset of result rows to be returned, in which each 194 + result row is different. NULL values are not treated as distinct from each other. 195 + The default behavior is that all result rows be returned, which can be made explicit 196 + with the keyword ALL.</p> 197 + <p> 198 + The query is executed against one or more tables specified after the FROM keyword. 199 + If multiple tables names are separated by commas, then the query is against the 200 + cross join of the various tables. The full SQL-92 join syntax can also be used to 201 + specify joins. A sub-query in parentheses may be substituted for any table name 202 + in the FROM clause. The entire FROM clause may be omitted, in which case the result 203 + is a single row consisting of the values of the expression list. 204 + </p> 205 + <p> 206 + The WHERE clause can be used to limit the number of rows over which the query operates.</p> 207 + <p> 208 + The GROUP BY clauses causes one or more rows of the result to be combined into a 209 + single row of output. This is especially useful when the result contains aggregate 210 + functions. The expressions in the GROUP BY clause do <em>not</em> have to be expressions 211 + that appear in the result. The HAVING clause is similar to WHERE except that HAVING 212 + applies after grouping has occurred. The HAVING expression may refer to values, 213 + even aggregate functions, that are not in the result.</p> 214 + <p> 215 + The ORDER BY clause causes the output rows to be sorted. The argument to ORDER BY 216 + is a list of expressions that are used as the key for the sort. The expressions 217 + do not have to be part of the result for a simple SELECT, but in a compound SELECT 218 + each sort expression must exactly match one of the result columns. Each sort expression 219 + may be optionally followed by a COLLATE keyword and the name of a collating function 220 + used for ordering text and/or keywords ASC or DESC to specify the sort order.</p> 221 + <p> 222 + The LIMIT clause places an upper bound on the number of rows returned in the result. 223 + A negative LIMIT indicates no upper bound. The optional OFFSET following LIMIT specifies 224 + how many rows to skip at the beginning of the result set. In a compound query, the 225 + LIMIT clause may only appear on the final SELECT statement. The limit is applied 226 + to the entire query not to the individual SELECT statement to which it is attached. 227 + Note that if the OFFSET keyword is used in the LIMIT clause, then the limit is the 228 + first number and the offset is the second number. If a comma is used instead of 229 + the OFFSET keyword, then the offset is the first number and the limit is the second 230 + number. This seeming contradition is intentional - it maximizes compatibility with 231 + legacy SQL database systems. 232 + </p> 233 + <p> 234 + A compound SELECT is formed from two or more simple SELECTs connected by one of 235 + the operators UNION, UNION ALL, INTERSECT, or EXCEPT. In a compound SELECT, all 236 + the constituent SELECTs must specify the same number of result columns. There may 237 + be only a single ORDER BY clause at the end of the compound SELECT. The UNION and 238 + UNION ALL operators combine the results of the SELECTs to the right and left into 239 + a single big table. The difference is that in UNION all result rows are distinct 240 + where in UNION ALL there may be duplicates. The INTERSECT operator takes the intersection 241 + of the results of the left and right SELECTs. EXCEPT takes the result of left SELECT 242 + after removing the results of the right SELECT. When three or more SELECTs are connected 243 + into a compound, they group from left to right.</p> 244 + <p> 245 + <hr> 246 + </p> 247 + <div id="footer"> 248 + <p> 249 + </p> 250 + <p> 251 + </p> 252 + </div> 253 + </div> 254 + </div> 255 + </body> 256 +</html>
Added Doc/Extra/lang_transaction.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>TRANSACTIONS</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">BEGIN TRANSACTION</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + BEGIN TRANSACTION</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">BEGIN </font></b>[<b><font color="#2c2cf0"> DEFERRED </font> 67 + </b><big>|</big><b><font color="#2c2cf0"> IMMEDIATE </font></b><big>|</big><b><font 68 + color="#2c2cf0"> EXCLUSIVE </font></b>]<b><font color="#2c2cf0"> </font></b>[<b><font 69 + color="#2c2cf0">TRANSACTION </font></b>[<b><font color="#2c2cf0"></font></b><i><font 70 + color="#ff3434">name</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b>]<b><font 71 + color="#2c2cf0"></font></b></td> 72 + </tr> 73 + </table> 74 + <table cellpadding="10"> 75 + <tr> 76 + <td align="right" valign="top"> 77 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 78 + <td> 79 + <b><font color="#2c2cf0">END </font></b>[<b><font color="#2c2cf0">TRANSACTION </font> 80 + </b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">name</font></i><b><font 81 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 82 + </tr> 83 + </table> 84 + <table cellpadding="10"> 85 + <tr> 86 + <td align="right" valign="top"> 87 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 88 + <td> 89 + <b><font color="#2c2cf0">COMMIT </font></b>[<b><font color="#2c2cf0">TRANSACTION </font> 90 + </b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">name</font></i><b><font 91 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 92 + </tr> 93 + </table> 94 + <table cellpadding="10"> 95 + <tr> 96 + <td align="right" valign="top"> 97 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 98 + <td> 99 + <b><font color="#2c2cf0">ROLLBACK </font></b>[<b><font color="#2c2cf0">TRANSACTION 100 + </font></b>[<b><font color="#2c2cf0"></font></b><i><font color="#ff3434">name</font></i><b><font 101 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 102 + </tr> 103 + </table> 104 + </p> 105 + <p> 106 + Beginning in version 2.0, SQLite supports transactions with rollback and atomic 107 + commit.</p> 108 + <p> 109 + The optional transaction name is ignored. SQLite currently does not allow nested 110 + transactions.</p> 111 + <p> 112 + No changes can be made to the database except within a transaction. Any command 113 + that changes the database (basically, any SQL command 114 + other than SELECT) will automatically start a transaction if one is not already in effect. Automatically started transactions 115 + are committed at the conclusion of the command. 116 + </p> 117 + <p> 118 + Transactions can be started manually using the BEGIN command. Such transactions 119 + usually persist until the next COMMIT or ROLLBACK command. But a transaction will 120 + also ROLLBACK if the database is closed or if an error occurs and the ROLLBACK conflict 121 + resolution algorithm is specified. See the documentation on the <a href="lang_conflict.html"> 122 + ON CONFLICT</a> clause for additional information about the ROLLBACK conflict 123 + resolution algorithm. 124 + </p> 125 + <p> 126 + In SQLite version 3.0.8 and later, transactions can be deferred, immediate, or exclusive. 127 + Deferred means that no locks are acquired on the database until the database is 128 + first accessed. Thus with a deferred transaction, the BEGIN statement itself does 129 + nothing. Locks are not acquired until the first read or write operation. The first 130 + read operation against a database creates a SHARED lock and the first write operation 131 + creates a RESERVED lock. Because the acquisition of locks is deferred until they 132 + are needed, it is possible that another thread or process could create a separate 133 + transaction and write to the database after the BEGIN on the current thread has 134 + executed. If the transaction is immediate, then RESERVED locks are acquired on all 135 + databases as soon as the BEGIN command is executed, without waiting for the database 136 + to be used. After a BEGIN IMMEDIATE, you are guaranteed that no other thread or 137 + process will be able to write to the database or do a BEGIN IMMEDIATE or BEGIN EXCLUSIVE. 138 + Other processes can continue to read from the database, however. An exclusive transaction 139 + causes EXCLUSIVE locks to be acquired on all databases. After a BEGIN EXCLUSIVE, 140 + you are guaranteed that no other thread or process will be able to read or write 141 + the database until the transaction is complete. 142 + </p> 143 + <p> 144 + A description of the meaning of SHARED, RESERVED, and EXCLUSIVE locks is available 145 + <a href="lockingv3.html">separately</a>. 146 + </p> 147 + <p> 148 + The default behavior for SQLite version 3.0.8 is a deferred transaction. For SQLite 149 + version 3.0.0 through 3.0.7, deferred is the only kind of transaction available. 150 + For SQLite version 2.8 and earlier, all transactions are exclusive. 151 + </p> 152 + <p> 153 + The COMMIT command does not actually perform a commit until all pending SQL commands 154 + finish. Thus if two or more SELECT statements are in the middle of processing and 155 + a COMMIT is executed, the commit will not actually occur until all SELECT statements 156 + finish. 157 + </p> 158 + <p> 159 + An attempt to execute COMMIT might result in an SQLITE_BUSY return code. This indicates 160 + that another thread or process had a read lock on the database that prevented the 161 + database from being updated. When COMMIT fails in this way, the transaction remains 162 + active and the COMMIT can be retried later after the reader has had a chance to 163 + clear. 164 + </p> 165 + <p> 166 + <hr> 167 + </p> 168 + <div id="footer"> 169 + <p> 170 + </p> 171 + <p> 172 + </p> 173 + </div> 174 + </div> 175 + </div> 176 + </body> 177 +</html>
Added Doc/Extra/lang_update.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>UPDATE</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + UPDATE </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + UPDATE</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">UPDATE </font></b>[<b><font color="#2c2cf0"> OR </font></b> 67 + <i><font color="#ff3434">conflict-algorithm</font></i><b><font color="#2c2cf0"> </font> 68 + </b>]<b><font color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0"></font></b><i><font 69 + color="#ff3434">database-name</font></i><b><font color="#2c2cf0"> <big>.</big></font></b>]<b><font 70 + color="#2c2cf0"> </font></b><i><font color="#ff3434">table-name</font></i><b><font 71 + color="#2c2cf0"><br /> 72 + SET </font></b><i><font color="#ff3434">assignment</font></i><b><font color="#2c2cf0"> 73 + </font></b>[<b><font color="#2c2cf0"><big>,</big> </font></b><i><font color="#ff3434"> 74 + assignment</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b><big>*</big><b><font 75 + color="#2c2cf0"><br /> 76 + </font></b>[<b><font color="#2c2cf0">WHERE </font></b><i><font color="#ff3434">expr</font></i><b><font 77 + color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"></font></b></td> 78 + </tr> 79 + <tr> 80 + <td align="right" valign="top"> 81 + <i><font color="#ff3434">assignment</font></i> ::=</td> 82 + <td> 83 + <b><font color="#2c2cf0"></font></b><i><font color="#ff3434">column-name</font></i><b><font 84 + color="#2c2cf0"> <big>=</big> </font></b><i><font color="#ff3434">expr</font></i><b><font 85 + color="#2c2cf0"></font></b></td> 86 + </tr> 87 + </table> 88 + </p> 89 + <p> 90 + The UPDATE statement is used to change the value of columns in selected rows of 91 + a table. Each assignment in an UPDATE specifies a column 92 + name to the left of the 93 + equals sign and an arbitrary expression to the right. The expressions may use the 94 + values of 95 + other columns. All expressions are evaluated before any assignments are 96 + made. A WHERE clause can be used to restrict which rows are updated.</p> 97 + <p> 98 + The optional conflict-clause allows the specification of an alternative constraint conflict resolution algorithm to use during this one command. See the section titled 99 + <a href="lang_conflict.html">ON CONFLICT</a> for additional information.</p> 100 + <p> 101 + <hr> 102 + </p> 103 + <div id="footer"> 104 + <p> 105 + </p> 106 + <p> 107 + </p> 108 + </div> 109 + </div> 110 + </div> 111 + </body> 112 +</html>
Added Doc/Extra/lang_vacuum.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>VACUUM</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + VACUUM </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + VACUUM</h4> 60 + <p> 61 + <table cellpadding="10"> 62 + <tr> 63 + <td align="right" valign="top"> 64 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 65 + <td> 66 + <b><font color="#2c2cf0">VACUUM </font></b>[<b><font color="#2c2cf0"></font></b><i><font 67 + color="#ff3434">index-or-table-name</font></i><b><font color="#2c2cf0"></font></b>]<b><font 68 + color="#2c2cf0"></font></b></td> 69 + </tr> 70 + </table> 71 + </p> 72 + <p> 73 + The VACUUM command is an SQLite extension modeled after a similar command found 74 + in PostgreSQL. If VACUUM is invoked with the name of a table or index then it is 75 + suppose to clean up the named table or index. In version 1.0 of SQLite, the VACUUM 76 + command would invoke <b>gdbm_reorganize()</b> to clean up the backend database file.</p> 77 + <p> 78 + VACUUM became a no-op when the GDBM backend was removed from SQLITE in version 2.0.0. 79 + VACUUM was reimplemented in version 2.8.1. The index or table name argument is now 80 + ignored. 81 + </p> 82 + <p> 83 + When an object (table, index, or trigger) is dropped from the database, it leaves 84 + behind empty space. This makes the database file larger than it needs to be, but 85 + can speed up inserts. In time inserts and deletes can leave the database file structure 86 + fragmented, which slows down disk access to the database contents. The VACUUM command 87 + cleans the main database by copying its contents to a temporary database file and 88 + reloading the original database file from the copy. This eliminates free pages, 89 + aligns table data to be contiguous, and otherwise cleans up the database file structure. 90 + It is not possible to perform the same process on an attached database file.</p> 91 + <p> 92 + This command will fail if there is an active transaction. This command has no effect 93 + on an in-memory database.</p> 94 + <p> 95 + As of SQLite version 3.1, an alternative to using the VACUUM command is auto-vacuum 96 + mode, enabled using the <a href="pragma.html#pragma_auto_vacuum">auto_vacuum pragma</a>.</p> 97 + <p> 98 + <hr> 99 + </p> 100 + <div id="footer"> 101 + <p> 102 + </p> 103 + <p> 104 + </p> 105 + </div> 106 + </div> 107 + </div> 108 + </body> 109 +</html>
Added Doc/Extra/pragma.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>PRAGMA</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">PRAGMA</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <h4> 59 + PRAGMA</h4> 60 + <p> 61 + The <a href="#syntax">PRAGMA command</a> is a special command used to modify the 62 + operation of the SQLite library or to query the library for internal (non-table) 63 + data. The PRAGMA command is issued using the same interface as other SQLite commands 64 + (e.g. SELECT, INSERT) but is different in the following important respects: 65 + </p> 66 + <ul> 67 + <li>Specific pragma statements may be removed and others added in future releases 68 + of SQLite. Use with caution! </li> 69 + <li>No error messages are generated if an unknown pragma is issued. Unknown pragmas 70 + are simply ignored. This means if there is a typo in a pragma statement the library 71 + does not inform the user of the fact. </li> 72 + <li>Some pragmas take effect during the SQL compilation stage, not the execution stage. 73 + This means if using the C-language sqlite3_compile(), sqlite3_step(), sqlite3_finalize() 74 + API (or similar in a wrapper interface), the pragma may be applied to the library 75 + during the sqlite3_compile() call. </li> 76 + <li>The pragma command is unlikely to be compatible with any other SQL engine. </li> 77 + </ul> 78 + <p> 79 + The available pragmas fall into four basic categories:</p> 80 + <ul> 81 + <li>Pragmas used to <a href="#schema">query the schema</a> of the current database. 82 + </li> 83 + <li>Pragmas used to <a href="#modify">modify the operation</a> of the SQLite library 84 + in some manner, or to query for the current mode of operation. </li> 85 + <li>Pragmas used to <a href="#version">query or modify the databases two version values</a>, 86 + the schema-version and the user-version. </li> 87 + <li>Pragmas used to <a href="#debug">debug the library</a> and verify that database 88 + files are not corrupted. </li> 89 + </ul> 90 + <hr /> 91 + <a name="syntax"></a> 92 + <h1> 93 + PRAGMA command syntax</h1> 94 + <p> 95 + <table cellpadding="10"> 96 + <tr> 97 + <td align="right" valign="top"> 98 + <i><font color="#ff3434">sql-statement</font></i> ::=</td> 99 + <td> 100 + <b><font color="#2c2cf0">PRAGMA </font></b><i><font color="#ff3434">name</font></i><b><font 101 + color="#2c2cf0"> </font></b>[<b><font color="#2c2cf0">= </font></b><i><font color="#ff3434"> 102 + value</font></i><b><font color="#2c2cf0"></font></b>]<b><font color="#2c2cf0"> </font> 103 + </b><big>|</big><b><font color="#2c2cf0"><br /> 104 + PRAGMA </font></b><i><font color="#ff3434">function</font></i><b><font color="#2c2cf0"><big>(</big></font></b><i><font 105 + color="#ff3434">arg</font></i><b><font color="#2c2cf0"><big>)</big></font></b></td> 106 + </tr> 107 + </table> 108 + </p> 109 + <p> 110 + The pragmas that take an integer <b><i>value</i></b> also accept symbolic names. 111 + The strings "<b>on</b>", "<b>true</b>", and "<b>yes</b>" are equivalent to <b>1</b>. 112 + The strings "<b>off</b>", "<b>false</b>", and "<b>no</b>" are equivalent to <b>0</b>. 113 + These strings are case- insensitive, and do not require quotes. An unrecognized 114 + string will be treated as <b>1</b>, and will not generate an error. When the <i>value</i> 115 + is returned it is as an integer.</p> 116 + <hr /> 117 + <a name="modify"></a> 118 + <h1> 119 + Pragmas to modify library operation</h1> 120 + <ul> 121 + <a name="pragma_auto_vacuum"></a> 122 + <li> 123 + <p> 124 + <b>PRAGMA auto_vacuum; 125 + <br /> 126 + PRAGMA auto_vacuum = </b><i>0 | 1</i><b>;</b></p> 127 + <p> 128 + Query or set the auto-vacuum flag in the database.</p> 129 + <p> 130 + Normally, when a transaction that deletes data from a database is committed, the 131 + database file remains the same size. Unused database file pages are marked as such 132 + and reused later on, when data is inserted into the database. In this mode the <a 133 + href="lang_vacuum.html">VACUUM</a> command is used to reclaim unused space.</p> 134 + <p> 135 + When the auto-vacuum flag is set, the database file shrinks when a transaction that 136 + deletes data is committed (The VACUUM command is not useful in a database with the 137 + auto-vacuum flag set). To support this functionality the database stores extra information 138 + internally, resulting in slightly larger database files than would otherwise be 139 + possible.</p> 140 + <p> 141 + It is only possible to modify the value of the auto-vacuum flag before any tables 142 + have been created in the database. No error message is returned if an attempt to 143 + modify the auto-vacuum flag is made after one or more tables have been created. 144 + </p> 145 + <a name="pragma_cache_size"></a></li> 146 + <li> 147 + <p> 148 + <b>PRAGMA cache_size; 149 + <br /> 150 + PRAGMA cache_size = </b><i>Number-of-pages</i><b>;</b></p> 151 + <p> 152 + Query or change the maximum number of database disk pages that SQLite will hold 153 + in memory at once. Each page uses about 1.5K of memory. The default cache size is 154 + 2000. If you are doing UPDATEs or DELETEs that change many rows of a database and 155 + you do not mind if SQLite uses more memory, you can increase the cache size for 156 + a possible speed improvement.</p> 157 + <p> 158 + When you change the cache size using the cache_size pragma, the change only endures 159 + for the current session. The cache size reverts to the default value when the database 160 + is closed and reopened. Use the <a href="#pragma_default_cache_size"><b>default_cache_size</b></a> 161 + pragma to check the cache size permanently.</p> 162 + <a name="pragma_case_sensitive_like"></a></li> 163 + <li> 164 + <p> 165 + <b>PRAGMA case_sensitive_like; 166 + <br /> 167 + PRAGMA case_sensitive_like = </b><i>0 | 1</i><b>;</b></p> 168 + <p> 169 + The default behavior of the LIKE operator is to ignore case for latin1 characters. 170 + Hence, by default <b>'a' LIKE 'A'</b> is true. The case_sensitive_like pragma can 171 + be turned on to change this behavior. When case_sensitive_like is enabled, <b>'a' 172 + LIKE 'A'</b> is false but <b>'a' LIKE 'a'</b> is still true.</p> 173 + <a name="pragma_count_changes"></a></li> 174 + <li> 175 + <p> 176 + <b>PRAGMA count_changes; 177 + <br /> 178 + PRAGMA count_changes = </b><i>0 | 1</i><b>;</b></p> 179 + <p> 180 + Query or change the count-changes flag. Normally, when the count-changes flag is 181 + not set, INSERT, UPDATE and DELETE statements return no data. When count-changes 182 + is set, each of these commands returns a single row of data consisting of one integer 183 + value - the number of rows inserted, modified or deleted by the command. The returned 184 + change count does not include any insertions, modifications or deletions performed 185 + by triggers.</p> 186 + <a name="pragma_default_cache_size"></a></li> 187 + <li> 188 + <p> 189 + <b>PRAGMA default_cache_size; 190 + <br /> 191 + PRAGMA default_cache_size = </b><i>Number-of-pages</i><b>;</b></p> 192 + <p> 193 + Query or change the maximum number of database disk pages that SQLite will hold 194 + in memory at once. Each page uses 1K on disk and about 1.5K in memory. This pragma 195 + works like the <a href="#pragma_cache_size"><b>cache_size</b></a> pragma with the 196 + additional feature that it changes the cache size persistently. With this pragma, 197 + you can set the cache size once and that setting is retained and reused every time 198 + you reopen the database.</p> 199 + <a name="pragma_default_synchronous"></a></li> 200 + <li> 201 + <p> 202 + <b>PRAGMA default_synchronous;</b></p> 203 + <p> 204 + This pragma was available in version 2.8 but was removed in version 3.0. It is a 205 + dangerous pragma whose use is discouraged. To help dissuide users of version 2.8 206 + from employing this pragma, the documentation will not tell you what it does.</p> 207 + <a name="pragma_empty_result_callbacks"></a></li> 208 + <li> 209 + <p> 210 + <b>PRAGMA empty_result_callbacks; 211 + <br /> 212 + PRAGMA empty_result_callbacks = </b><i>0 | 1</i><b>;</b></p> 213 + <p> 214 + Query or change the empty-result-callbacks flag.</p> 215 + <p> 216 + The empty-result-callbacks flag affects the sqlite3_exec API only. Normally, when 217 + the empty-result-callbacks flag is cleared, the callback function supplied to the 218 + sqlite3_exec() call is not invoked for commands that return zero rows of data. When 219 + empty-result-callbacks is set in this situation, the callback function is invoked 220 + exactly once, with the third parameter set to 0 (NULL). This is to enable programs 221 + that use the sqlite3_exec() API to retrieve column-names even when a query returns 222 + no data. 223 + </p> 224 + <a name="pragma_encoding"></a></li> 225 + <li> 226 + <p> 227 + <b>PRAGMA encoding; 228 + <br /> 229 + PRAGMA encoding = "UTF-8"; 230 + <br /> 231 + PRAGMA encoding = "UTF-16"; 232 + <br /> 233 + PRAGMA encoding = "UTF-16le"; 234 + <br /> 235 + PRAGMA encoding = "UTF-16be";</b></p> 236 + <p> 237 + In first form, if the main database has already been created, then this pragma returns 238 + the text encoding used by the main database, one of "UTF-8", "UTF-16le" (little-endian 239 + UTF-16 encoding) or "UTF-16be" (big-endian UTF-16 encoding). If the main database 240 + has not already been created, then the value returned is the text encoding that 241 + will be used to create the main database, if it is created by this session.</p> 242 + <p> 243 + The second and subsequent forms of this pragma are only useful if the main database 244 + has not already been created. In this case the pragma sets the encoding that the 245 + main database will be created with if it is created by this session. The string 246 + "UTF-16" is interpreted as "UTF-16 encoding using native machine byte-ordering". 247 + If the second and subsequent forms are used after the database file has already 248 + been created, they have no effect and are silently ignored.</p> 249 + <p> 250 + Once an encoding has been set for a database, it cannot be changed.</p> 251 + <p> 252 + Databases created by the ATTACH command always use the same encoding as the main 253 + database.</p> 254 + <a name="pragma_full_column_names"></a></li> 255 + <li> 256 + <p> 257 + <b>PRAGMA full_column_names; 258 + <br /> 259 + PRAGMA full_column_names = </b><i>0 | 1</i><b>;</b></p> 260 + <p> 261 + Query or change the full-column-names flag. This flag affects the way SQLite names 262 + columns of data returned by SELECT statements when the expression for the column 263 + is a table-column name or the wildcard "*". Normally, such result columns are named 264 + <table-name/alias><column-name> if the SELECT statement joins two or 265 + more tables together, or simply <column-name> if the SELECT statement queries 266 + a single table. When the full-column-names flag is set, such columns are always 267 + named <table-name/alias> <column-name> regardless of whether or not 268 + a join is performed. 269 + </p> 270 + <p> 271 + If both the short-column-names and full-column-names are set, then the behaviour 272 + associated with the full-column-names flag is exhibited. 273 + </p> 274 + <a name="pragma_fullfsync"></a></li> 275 + <li> 276 + <p> 277 + <b>PRAGMA fullfsync 278 + <br /> 279 + PRAGMA fullfsync = </b><i>0 | 1</i><b>;</b></p> 280 + <p> 281 + Query or change the fullfsync flag. This flag affects determines whether or not 282 + the F_FULLFSYNC syncing method is used on systems that support it. The default value 283 + is off. As of this writing (2006-02-10) only Mac OS X supports F_FULLFSYNC. 284 + </p> 285 + <a name="pragma_legacy_file_format"></a></li> 286 + <li> 287 + <p> 288 + <b>PRAGMA legacy_file_format; 289 + <br /> 290 + PRAGMA legacy_file_format = <i>ON | OFF</i></b></p> 291 + <p> 292 + This pragma sets or queries the value of the legacy_file_format flag. When this 293 + flag is on, new SQLite databases are created in a file format that is readable and 294 + writable by all versions of SQLite going back to 3.0.0. When the flag is off, new 295 + databases are created using the latest file format which might to be readable or 296 + writable by older versions of SQLite.</p> 297 + <p> 298 + This flag only effects newly created databases. It has no effect on databases that 299 + already exists.</p> 300 + <a name="pragma_page_size"></a></li> 301 + <li> 302 + <p> 303 + <b>PRAGMA page_size; 304 + <br /> 305 + PRAGMA page_size = </b><i>bytes</i><b>;</b></p> 306 + <p> 307 + Query or set the page-size of the database. The page-size may only be set if the 308 + database has not yet been created. The page size must be a power of two greater 309 + than or equal to 512 and less than or equal to 8192. The upper limit may be modified 310 + by setting the value of macro SQLITE_MAX_PAGE_SIZE during compilation. The maximum 311 + upper bound is 32768. 312 + </p> 313 + <a name="pragma_read_uncommitted"></a></li> 314 + <li> 315 + <p> 316 + <b>PRAGMA read_uncommitted; 317 + <br /> 318 + PRAGMA read_uncommitted = </b><i>0 | 1</i><b>;</b></p> 319 + <p> 320 + Query, set, or clear READ UNCOMMITTED isolation. The default isolation level for 321 + SQLite is SERIALIZABLE. Any process or thread can select READ UNCOMMITTED isolation, 322 + but SERIALIZABLE will still be used except between connections that share a common 323 + page and schema cache. Cache sharing is enabled using the <a href="capi3ref.html#sqlite3_enable_shared_cache"> 324 + sqlite3_enable_shared_cache()</a> API and is only available between connections 325 + running the same thread. Cache sharing is off by default. 326 + </p> 327 + <a name="pragma_short_column_names"></a></li> 328 + <li> 329 + <p> 330 + <b>PRAGMA short_column_names; 331 + <br /> 332 + PRAGMA short_column_names = </b><i>0 | 1</i><b>;</b></p> 333 + <p> 334 + Query or change the short-column-names flag. This flag affects the way SQLite names 335 + columns of data returned by SELECT statements when the expression for the column 336 + is a table-column name or the wildcard "*". Normally, such result columns are named 337 + <table-name/alias>lt;column-name> if the SELECT statement joins two or 338 + more tables together, or simply <column-name> if the SELECT statement queries 339 + a single table. When the short-column-names flag is set, such columns are always 340 + named <column-name> regardless of whether or not a join is performed. 341 + </p> 342 + <p> 343 + If both the short-column-names and full-column-names are set, then the behaviour 344 + associated with the full-column-names flag is exhibited. 345 + </p> 346 + <a name="pragma_synchronous"></a></li> 347 + <li> 348 + <p> 349 + <b>PRAGMA synchronous; 350 + <br /> 351 + PRAGMA synchronous = FULL; </b>(2)<b> 352 + <br /> 353 + PRAGMA synchronous = NORMAL; </b>(1)<b> 354 + <br /> 355 + PRAGMA synchronous = OFF; </b>(0)</p> 356 + <p> 357 + Query or change the setting of the "synchronous" flag. The first (query) form will 358 + return the setting as an integer. When synchronous is FULL (2), the SQLite database 359 + engine will pause at critical moments to make sure that data has actually been written 360 + to the disk surface before continuing. This ensures that if the operating system 361 + crashes or if there is a power failure, the database will be uncorrupted after rebooting. 362 + FULL synchronous is very safe, but it is also slow. When synchronous is NORMAL, 363 + the SQLite database engine will still pause at the most critical moments, but less 364 + often than in FULL mode. There is a very small (though non-zero) chance that a power 365 + failure at just the wrong time could corrupt the database in NORMAL mode. But in 366 + practice, you are more likely to suffer a catastrophic disk failure or some other 367 + unrecoverable hardware fault. With synchronous OFF (0), SQLite continues without 368 + pausing as soon as it has handed data off to the operating system. If the application 369 + running SQLite crashes, the data will be safe, but the database might become corrupted 370 + if the operating system crashes or the computer loses power before that data has 371 + been written to the disk surface. On the other hand, some operations are as much 372 + as 50 or more times faster with synchronous OFF. 373 + </p> 374 + <p> 375 + In SQLite version 2, the default value is NORMAL. For version 3, the default was 376 + changed to FULL. 377 + </p> 378 + <a name="pragma_temp_store"></a></li> 379 + <li> 380 + <p> 381 + <b>PRAGMA temp_store; 382 + <br /> 383 + PRAGMA temp_store = DEFAULT;</b> (0)<b> 384 + <br /> 385 + PRAGMA temp_store = FILE;</b> (1)<b> 386 + <br /> 387 + PRAGMA temp_store = MEMORY;</b> (2)</p> 388 + <p> 389 + Query or change the setting of the "<b>temp_store</b>" parameter. When temp_store 390 + is DEFAULT (0), the compile-time C preprocessor macro TEMP_STORE is used to determine 391 + where temporary tables and indices are stored. When temp_store is MEMORY (2) temporary 392 + tables and indices are kept in memory. When temp_store is FILE (1) temporary tables 393 + and indices are stored in a file. The <a href="#pragma_temp_store_directory">temp_store_directory</a> 394 + pragma can be used to specify the directory containing this file. <b>FILE</b> is 395 + specified. When the temp_store setting is changed, all existing temporary tables, 396 + indices, triggers, and views are immediately deleted.</p> 397 + <p> 398 + It is possible for the library compile-time C preprocessor symbol TEMP_STORE to 399 + override this pragma setting. The following table summarizes the interaction of 400 + the TEMP_STORE preprocessor macro and the temp_store pragma:</p> 401 + <blockquote> 402 + <table border="1" cellpadding="2"> 403 + <tr> 404 + <th valign="bottom"> 405 + TEMP_STORE</th> 406 + <th valign="bottom"> 407 + PRAGMA<br /> 408 + temp_store</th> 409 + <th> 410 + Storage used for<br /> 411 + TEMP tables and indices</th> 412 + </tr> 413 + <tr> 414 + <td align="middle"> 415 + 0</td> 416 + <td align="middle"> 417 + <em>any</em></td> 418 + <td align="middle"> 419 + file</td> 420 + </tr> 421 + <tr> 422 + <td align="middle"> 423 + 1</td> 424 + <td align="middle"> 425 + 0</td> 426 + <td align="middle"> 427 + file</td> 428 + </tr> 429 + <tr> 430 + <td align="middle"> 431 + 1</td> 432 + <td align="middle"> 433 + 1</td> 434 + <td align="middle"> 435 + file</td> 436 + </tr> 437 + <tr> 438 + <td align="middle"> 439 + 1</td> 440 + <td align="middle"> 441 + 2</td> 442 + <td align="middle"> 443 + memory</td> 444 + </tr> 445 + <tr> 446 + <td align="middle"> 447 + 2</td> 448 + <td align="middle"> 449 + 0</td> 450 + <td align="middle"> 451 + memory</td> 452 + </tr> 453 + <tr> 454 + <td align="middle"> 455 + 2</td> 456 + <td align="middle"> 457 + 1</td> 458 + <td align="middle"> 459 + file</td> 460 + </tr> 461 + <tr> 462 + <td align="middle"> 463 + 2</td> 464 + <td align="middle"> 465 + 2</td> 466 + <td align="middle"> 467 + memory</td> 468 + </tr> 469 + <tr> 470 + <td align="middle"> 471 + 3</td> 472 + <td align="middle"> 473 + <em>any</em></td> 474 + <td align="middle"> 475 + memory</td> 476 + </tr> 477 + </table> 478 + </blockquote> 479 + <br /> 480 + <a name="pragma_temp_store_directory"></a></li> 481 + <li> 482 + <p> 483 + <b>PRAGMA temp_store_directory; 484 + <br /> 485 + PRAGMA temp_store_directory = 'directory-name';</b></p> 486 + <p> 487 + Query or change the setting of the "temp_store_directory" - the directory where 488 + files used for storing temporary tables and indices are kept. This setting lasts 489 + for the duration of the current connection only and resets to its default value 490 + for each new connection opened. 491 + </p> 492 + <p> 493 + When the temp_store_directory setting is changed, all existing temporary tables, 494 + indices, triggers, and viewers are immediately deleted. In practice, temp_store_directory 495 + should be set immediately after the database is opened. 496 + </p> 497 + <p> 498 + The value <i>directory-name</i> should be enclosed in single quotes. To revert the 499 + directory to the default, set the <i>directory-name</i> to an empty string, e.g., 500 + <i>PRAGMA temp_store_directory = ''</i>. An error is raised if <i>directory-name</i> 501 + is not found or is not writable. 502 + </p> 503 + <p> 504 + The default directory for temporary files depends on the OS. For Unix/Linux/OSX, 505 + the default is the is the first writable directory found in the list of: <b>/var/tmp, 506 + /usr/tmp, /tmp,</b> and <b><i>current-directory</i></b>. For Windows NT, the default 507 + directory is determined by Windows, generally <b>C:\Documents and Settings\<i>user-name</i>\Local 508 + Settings\Temp\</b>. Temporary files created by SQLite are unlinked immediately 509 + after opening, so that the operating system can automatically delete the files when 510 + the SQLite process exits. Thus, temporary files are not normally visible through 511 + <i>ls</i> or <i>dir</i> commands.</p> 512 + </li> 513 + </ul> 514 + <hr /> 515 + <a name="schema"></a> 516 + <h1> 517 + Pragmas to query the database schema</h1> 518 + <ul> 519 + <a name="pragma_database_list"></a> 520 + <li> 521 + <p> 522 + <b>PRAGMA database_list;</b></p> 523 + <p> 524 + For each open database, invoke the callback function once with information about 525 + that database. Arguments include the index and the name the database was attached 526 + with. The first row will be for the main database. The second row will be for the 527 + database used to store temporary tables.</p> 528 + <a name="pragma_foreign_key_list"></a></li> 529 + <li> 530 + <p> 531 + <b>PRAGMA foreign_key_list(</b><i>table-name</i><b>);</b></p> 532 + <p> 533 + For each foreign key that references a column in the argument table, invoke the 534 + callback function with information about that foreign key. The callback function 535 + will be invoked once for each column in each foreign key.</p> 536 + <a name="pragma_index_info"></a></li> 537 + <li> 538 + <p> 539 + <b>PRAGMA index_info(</b><i>index-name</i><b>);</b></p> 540 + <p> 541 + For each column that the named index references, invoke the callback function once 542 + with information about that column, including the column name, and the column number.</p> 543 + <a name="pragma_index_list"></a></li> 544 + <li> 545 + <p> 546 + <b>PRAGMA index_list(</b><i>table-name</i><b>);</b></p> 547 + <p> 548 + For each index on the named table, invoke the callback function once with information 549 + about that index. Arguments include the index name and a flag to indicate whether 550 + or not the index must be unique.</p> 551 + <a name="pragma_table_info"></a></li> 552 + <li> 553 + <p> 554 + <b>PRAGMA table_info(</b><i>table-name</i><b>);</b></p> 555 + <p> 556 + For each column in the named table, invoke the callback function once with information 557 + about that column, including the column name, data type, whether or not the column 558 + can be NULL, and the default value for the column.</p> 559 + </li> 560 + </ul> 561 + <hr /> 562 + <a name="version"></a> 563 + <h1> 564 + Pragmas to query/modify version values</h1> 565 + <ul> 566 + <a name="pragma_schema_version"></a><a name="pragma_user_version"></a> 567 + <li> 568 + <p> 569 + <b>PRAGMA [database.]schema_version; 570 + <br /> 571 + PRAGMA [database.]schema_version = </b><i>integer </i><b>; 572 + <br /> 573 + PRAGMA [database.]user_version; 574 + <br /> 575 + PRAGMA [database.]user_version = </b><i>integer </i><b>;</b> 576 + </p> 577 + <p> 578 + The pragmas schema_version and user_version are used to set or get the value of 579 + the schema-version and user-version, respectively. Both the schema-version and the 580 + user-version are 32-bit signed integers stored in the database header.</p> 581 + <p> 582 + The schema-version is usually only manipulated internally by SQLite. It is incremented 583 + by SQLite whenever the database schema is modified (by creating or dropping a table 584 + or index). The schema version is used by SQLite each time a query is executed to 585 + ensure that the internal cache of the schema used when compiling the SQL query matches 586 + the schema of the database against which the compiled query is actually executed. 587 + Subverting this mechanism by using "PRAGMA schema_version" to modify the schema-version 588 + is potentially dangerous and may lead to program crashes or database corruption. 589 + Use with caution!</p> 590 + <p> 591 + The user-version is not used internally by SQLite. It may be used by applications 592 + for any purpose.</p> 593 + </li> 594 + </ul> 595 + <hr /> 596 + <a name="debug"></a> 597 + <h1> 598 + Pragmas to debug the library</h1> 599 + <ul> 600 + <a name="pragma_integrity_check"></a> 601 + <li> 602 + <p> 603 + <b>PRAGMA integrity_check;</b></p> 604 + <p> 605 + The command does an integrity check of the entire database. It looks for out-of-order 606 + records, missing pages, malformed records, and corrupt indices. If any problems 607 + are found, then a single string is returned which is a description of all problems. 608 + If everything is in order, "ok" is returned.</p> 609 + <a name="pragma_parser_trace"></a></li> 610 + <li> 611 + <p> 612 + <b>PRAGMA parser_trace = ON; </b>(1)<b> 613 + <br /> 614 + PRAGMA parser_trace = OFF;</b> (0)</p> 615 + <p> 616 + Turn tracing of the SQL parser inside of the SQLite library on and off. This is 617 + used for debugging. This only works if the library is compiled without the NDEBUG 618 + macro. 619 + </p> 620 + <a name="pragma_vdbe_trace"></a></li> 621 + <li> 622 + <p> 623 + <b>PRAGMA vdbe_trace = ON; </b>(1)<b> 624 + <br /> 625 + PRAGMA vdbe_trace = OFF;</b> (0)</p> 626 + <p> 627 + Turn tracing of the virtual database engine inside of the SQLite library on and 628 + off. This is used for debugging. See the <a href="vdbe.html#trace">VDBE documentation</a> 629 + for more information.</p> 630 + <a name="pragma_vdbe_listing"></a></li> 631 + <li> 632 + <p> 633 + <b>PRAGMA vdbe_listing = ON; </b>(1)<b> 634 + <br /> 635 + PRAGMA vdbe_listing = OFF;</b> (0)</p> 636 + <p> 637 + Turn listings of virtual machine programs on and off. With listing is on, the entire 638 + content of a program is printed just prior to beginning execution. This is like 639 + automatically executing an EXPLAIN prior to each statement. The statement executes 640 + normally after the listing is printed. This is used for debugging. See the <a href="vdbe.html#trace"> 641 + VDBE documentation</a> for more information.</p> 642 + </li> 643 + </ul> 644 + <p> 645 + <hr> 646 + </p> 647 + <div id="footer"> 648 + <p> 649 + </p> 650 + <p> 651 + </p> 652 + </div> 653 + </div> 654 + </div> 655 + </body> 656 +</html>
Added Doc/Extra/syntax.html.
1 +<html dir="LTR" xmlns="http://www.w3.org/1999/xhtml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:ndoc="urn:ndoc-preprocess"> 2 + <head> 3 + <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> 4 + <title>SQLite Query Syntax</title> 5 + <link rel="stylesheet" type="text/css" href="ndoc.css"> </link> 6 + <link rel="stylesheet" type="text/css" href="user.css"> </link> 7 + <script type="text/javascript" src="ndoc.js"> </script> 8 + </head> 9 + <body style="display: none;"> 10 + <input type="hidden" id="userDataCache" class="userDataStyle" /> 11 + <input type="hidden" id="hiddenScrollOffset" /> 12 + <img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif" /> 13 + <img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif" /> 14 + <img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif" /> 15 + <img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif" /> 16 + <img id="collapseAllImage" style="display:none; height:0; width:0;" src="collall.gif" /> 17 + <img id="expandAllImage" style="display:none; height:0; width:0;" src="expall.gif" /> 18 + <img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif" /> 19 + <img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif" /> 20 + <div id="header"> 21 + <table width="100%" id="topTable"> 22 + <tr id="headerTableRow1"> 23 + <td align="left"> 24 + <span id="runningHeaderText">SQLite Query Syntax</span> </td> 25 + </tr> 26 + <tr id="headerTableRow2"> 27 + <td align="left"> 28 + <span id="nsrTitle">SQLite Language Reference Documentation</span> 29 + </td> 30 + </tr> 31 + <tr id="headerTableRow3" style="display:none"> 32 + <td> 33 + <a id="seeAlsoSectionLink" href="#seeAlsoToggle" onclick="OpenSection(seeAlsoToggle)">See Also</a> 34 + <a id="exampleSectionLink" href="#codeExampleToggle" onclick="OpenSection(codeExampleToggle)">Example</a> 35 + </td> 36 + </tr> 37 + </table> 38 + <table width="100%" id="bottomTable" cellspacing="0" cellpadding="0" style="display:none"> 39 + <tr> 40 + <td> 41 + <span onclick="ExpandCollapseAll(toggleAllImage)" style="cursor:default;" onkeypress="ExpandCollapseAll_CheckKey(toggleAllImage)" tabindex="0"> 42 + <img ID="toggleAllImage" class="toggleAll" src="collall.gif" /> 43 + <label id="collapseAllLabel" for="toggleAllImage" style="display: none;"> 44 + Collapse All 45 + </label> 46 + <label id="expandAllLabel" for="toggleAllImage" style="display: none;"> 47 + Expand All 48 + </label> 49 + </span> 50 + </td> 51 + </tr> 52 + </table> 53 + </div> 54 + <div id="mainSection"> 55 + <div id="mainBody"> 56 + <h1 class="heading"> 57 + SQL As Understood By SQLite</h1> 58 + <p> 59 + The SQLite library understands most of the standard SQL language. But it does omit 60 + some features while at the same time adding a few features of its own. This document 61 + attempts to describe precisely what parts of the SQL language SQLite does and does 62 + not support. A list of keywords is also provided. In all of the syntax diagrams 63 + that follow, literal text is shown in bold blue. Non-terminal symbols are shown 64 + in italic red. Operators that are part of the syntactic markup itself are shown 65 + in black roman. This document is just an overview of the SQL syntax implemented 66 + by SQLite. 67 + </p> 68 + <h4> 69 + SQLite implements the follow syntax:</h4> 70 + <p> 71 + <table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse"> 72 + <tr> 73 + <td> 74 + <a href="lang_altertable.html"> 75 + ALTER TABLE</a></td> 76 + </tr> 77 + <tr> 78 + <td> 79 + <a href="lang_analyze.html"> 80 + ANALYZE</a></td> 81 + </tr> 82 + <tr> 83 + <td style="height: 19px"> 84 + <a href="lang_attach.html"> 85 + ATTACH DATABASE</a></td> 86 + </tr> 87 + <tr> 88 + <td> 89 + <a href="lang_transaction.html"> 90 + BEGIN TRANSACTION</a></td> 91 + </tr> 92 + <tr> 93 + <td> 94 + <a href="lang_comment.html"> 95 + comment</a></td> 96 + </tr> 97 + <tr> 98 + <td> 99 + <a href="lang_transaction.html"> 100 + COMMIT TRANSACTION</a></td> 101 + </tr> 102 + <tr> 103 + <td> 104 + <a href="lang_createindex.html">CREATE INDEX</a></td> 105 + </tr> 106 + <tr> 107 + <td> 108 + <a href="lang_createtable.html">CREATE TABLE</a></td> 109 + </tr> 110 + <tr> 111 + <td> 112 + <a href="lang_createtrigger.html">CREATE TRIGGER</a></td> 113 + </tr> 114 + <tr> 115 + <td> 116 + <a href="lang_createview.html">CREATE VIEW</a></td> 117 + </tr> 118 + <tr> 119 + <td> 120 + <a href="lang_createvtab.html"> 121 + CREATE VIRTUAL TABLE</a></td> 122 + </tr> 123 + <tr> 124 + <td> 125 + <a href="lang_delete.html"> 126 + DELETE</a></td> 127 + </tr> 128 + <tr> 129 + <td> 130 + <a href="lang_detach.html"> 131 + DETACH DATABASE</a></td> 132 + </tr> 133 + <tr> 134 + <td> 135 + <a href="lang_dropindex.html">DROP INDEX</a></td> 136 + </tr> 137 + <tr> 138 + <td> 139 + <a href="lang_droptable.html">DROP TABLE</a></td> 140 + </tr> 141 + <tr> 142 + <td> 143 + <a href="lang_droptrigger.html">DROP TRIGGER</a></td> 144 + </tr> 145 + <tr> 146 + <td> 147 + <a href="lang_dropview.html">DROP VIEW</a></td> 148 + </tr> 149 + <tr> 150 + <td> 151 + <a href="lang_transaction.html"> 152 + END TRANSACTION</a></td> 153 + </tr> 154 + <tr> 155 + <td> 156 + <a href="lang_explain.html"> 157 + EXPLAIN</a></td> 158 + </tr> 159 + <tr> 160 + <td> 161 + <a href="lang_expr.html"> 162 + expression</a></td> 163 + </tr> 164 + <tr> 165 + <td> 166 + <a href="lang_insert.html"> 167 + INSERT</a></td> 168 + </tr> 169 + <tr> 170 + <td> 171 + <a href="lang_conflict.html"> 172 + ON CONFLICT clause</a></td> 173 + </tr> 174 + <tr> 175 + <td style="height: 19px"> 176 + <a href="pragma.html"> 177 + PRAGMA</a></td> 178 + </tr> 179 + <tr> 180 + <td> 181 + <a href="lang_reindex.html"> 182 + REINDEX</a></td> 183 + </tr> 184 + <tr> 185 + <td> 186 + <a href="lang_replace.html"> 187 + REPLACE</a></td> 188 + </tr> 189 + <tr> 190 + <td> 191 + <a href="lang_transaction.html"> 192 + ROLLBACK TRANSACTION</a></td> 193 + </tr> 194 + <tr> 195 + <td> 196 + <a href="lang_select.html"> 197 + SELECT</a></td> 198 + </tr> 199 + <tr> 200 + <td> 201 + <a href="lang_update.html"> 202 + UPDATE</a></td> 203 + </tr> 204 + <tr> 205 + <td> 206 + <a href="lang_vacuum.html"> 207 + VACUUM</a></td> 208 + </tr> 209 + </table> 210 + </p> 211 + <hr> 212 + <div id="footer"> 213 + <p> 214 + </p> 215 + <p> 216 + </p> 217 + </div> 218 + </div> 219 + </div> 220 + </body> 221 +</html>