Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | AUTOINCREMENT documentation added. Improvements to lang.html. (CVS 2129) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
ac72a1d5518f7b505ae2a1bd3be3d71d |
User & Date: | drh 2004-11-21 01:02:00.000 |
Context
2004-11-22
| ||
03:34 | Fix auth.test to work when SQLITE_OMIT_ALTERTABLE is defined. (CVS 2130) (check-in: 27a8379b54 user: danielk1977 tags: trunk) | |
2004-11-21
| ||
01:02 | AUTOINCREMENT documentation added. Improvements to lang.html. (CVS 2129) (check-in: ac72a1d551 user: drh tags: trunk) | |
2004-11-20
| ||
21:02 | Fix to the documentation on sqlite3_create_function. Ticket #899. (CVS 2128) (check-in: 4ab1d012f0 user: drh tags: trunk) | |
Changes
Changes to Makefile.in.
︙ | ︙ | |||
404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 | # arch.html: $(TOP)/www/arch.tcl tclsh $(TOP)/www/arch.tcl >arch.html arch2.gif: $(TOP)/www/arch2.gif cp $(TOP)/www/arch2.gif . c_interface.html: $(TOP)/www/c_interface.tcl tclsh $(TOP)/www/c_interface.tcl >c_interface.html capi3.html: $(TOP)/www/capi3.tcl tclsh $(TOP)/www/capi3.tcl >capi3.html capi3ref.html: $(TOP)/www/capi3ref.tcl tclsh $(TOP)/www/capi3ref.tcl >capi3ref.html changes.html: $(TOP)/www/changes.tcl tclsh $(TOP)/www/changes.tcl >changes.html copyright.html: $(TOP)/www/copyright.tcl tclsh $(TOP)/www/copyright.tcl >copyright.html copyright-release.html: $(TOP)/www/copyright-release.html cp $(TOP)/www/copyright-release.html . copyright-release.pdf: $(TOP)/www/copyright-release.pdf | > > > > > > | 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 | # arch.html: $(TOP)/www/arch.tcl tclsh $(TOP)/www/arch.tcl >arch.html arch2.gif: $(TOP)/www/arch2.gif cp $(TOP)/www/arch2.gif . autoinc.html: $(TOP)/www/autoinc.tcl tclsh $(TOP)/www/autoinc.tcl >autoinc.html c_interface.html: $(TOP)/www/c_interface.tcl tclsh $(TOP)/www/c_interface.tcl >c_interface.html capi3.html: $(TOP)/www/capi3.tcl tclsh $(TOP)/www/capi3.tcl >capi3.html capi3ref.html: $(TOP)/www/capi3ref.tcl tclsh $(TOP)/www/capi3ref.tcl >capi3ref.html changes.html: $(TOP)/www/changes.tcl tclsh $(TOP)/www/changes.tcl >changes.html compile.html: $(TOP)/www/compile.tcl tclsh $(TOP)/www/compile.tcl >compile.html copyright.html: $(TOP)/www/copyright.tcl tclsh $(TOP)/www/copyright.tcl >copyright.html copyright-release.html: $(TOP)/www/copyright-release.html cp $(TOP)/www/copyright-release.html . copyright-release.pdf: $(TOP)/www/copyright-release.pdf |
︙ | ︙ | |||
506 507 508 509 510 511 512 | tclsh $(TOP)/www/version3.tcl >version3.html # Files to be published on the website. # DOC = \ arch.html \ | | > > > | | 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 | tclsh $(TOP)/www/version3.tcl >version3.html # Files to be published on the website. # DOC = \ arch.html \ arch.png \ autoinc.html \ c_interface.html \ capi3.html \ capi3ref.html \ changes.html \ compile.html \ copyright.html \ copyright-release.html \ copyright-release.pdf \ conflict.html \ datatypes.html \ datatype3.html \ docs.html \ download.html \ faq.html \ fileformat.html \ formatchng.html \ index.html \ lang.html \ lockingv3.html \ mingw.html \ nulls.html \ oldnews.html \ omitted.html \ opcode.html \ pragma.html \ quickstart.html \ speed.html \ sqlite.gif \ sqlite.html \ support.html \ tclsqlite.html \ vdbe.html \ version3.html doc: common.tcl $(DOC) mkdir -p doc mv $(DOC) doc install: sqlite3 libsqlite3.la sqlite3.h $(INSTALL) -d $(DESTDIR)$(libdir) |
︙ | ︙ |
Changes to main.mk.
︙ | ︙ | |||
380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 | # arch.html: $(TOP)/www/arch.tcl tclsh $(TOP)/www/arch.tcl >arch.html arch.png: $(TOP)/www/arch.png cp $(TOP)/www/arch.png . c_interface.html: $(TOP)/www/c_interface.tcl tclsh $(TOP)/www/c_interface.tcl >c_interface.html capi3.html: $(TOP)/www/capi3.tcl tclsh $(TOP)/www/capi3.tcl >capi3.html capi3ref.html: $(TOP)/www/capi3ref.tcl tclsh $(TOP)/www/capi3ref.tcl >capi3ref.html changes.html: $(TOP)/www/changes.tcl tclsh $(TOP)/www/changes.tcl >changes.html copyright.html: $(TOP)/www/copyright.tcl tclsh $(TOP)/www/copyright.tcl >copyright.html copyright-release.html: $(TOP)/www/copyright-release.html cp $(TOP)/www/copyright-release.html . copyright-release.pdf: $(TOP)/www/copyright-release.pdf | > > > > > > | 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 | # arch.html: $(TOP)/www/arch.tcl tclsh $(TOP)/www/arch.tcl >arch.html arch.png: $(TOP)/www/arch.png cp $(TOP)/www/arch.png . autoinc.html: $(TOP)/www/autoinc.tcl tclsh $(TOP)/www/autoinc.tcl >autoinc.html c_interface.html: $(TOP)/www/c_interface.tcl tclsh $(TOP)/www/c_interface.tcl >c_interface.html capi3.html: $(TOP)/www/capi3.tcl tclsh $(TOP)/www/capi3.tcl >capi3.html capi3ref.html: $(TOP)/www/capi3ref.tcl tclsh $(TOP)/www/capi3ref.tcl >capi3ref.html changes.html: $(TOP)/www/changes.tcl tclsh $(TOP)/www/changes.tcl >changes.html compile.html: $(TOP)/www/compile.tcl tclsh $(TOP)/www/compile.tcl >compile.html copyright.html: $(TOP)/www/copyright.tcl tclsh $(TOP)/www/copyright.tcl >copyright.html copyright-release.html: $(TOP)/www/copyright-release.html cp $(TOP)/www/copyright-release.html . copyright-release.pdf: $(TOP)/www/copyright-release.pdf |
︙ | ︙ | |||
480 481 482 483 484 485 486 | vdbe.html: $(TOP)/www/vdbe.tcl tclsh $(TOP)/www/vdbe.tcl >vdbe.html version3.html: $(TOP)/www/version3.tcl tclsh $(TOP)/www/version3.tcl >version3.html | < < < > > | 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 | vdbe.html: $(TOP)/www/vdbe.tcl tclsh $(TOP)/www/vdbe.tcl >vdbe.html version3.html: $(TOP)/www/version3.tcl tclsh $(TOP)/www/version3.tcl >version3.html # Files to be published on the website. # DOC = \ arch.html \ arch.png \ autoinc.html \ c_interface.html \ capi3.html \ capi3ref.html \ changes.html \ compile.html \ copyright.html \ copyright-release.html \ copyright-release.pdf \ conflict.html \ datatypes.html \ datatype3.html \ docs.html \ |
︙ | ︙ | |||
520 521 522 523 524 525 526 | quickstart.html \ speed.html \ sqlite.gif \ sqlite.html \ support.html \ tclsqlite.html \ vdbe.html \ | | < | 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 | quickstart.html \ speed.html \ sqlite.gif \ sqlite.html \ support.html \ tclsqlite.html \ vdbe.html \ version3.html doc: common.tcl $(DOC) mkdir -p doc mv $(DOC) doc # Standard install and cleanup targets # |
︙ | ︙ |
Added www/autoinc.tcl.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 | # # Run this Tcl script to generate the autoinc.html file. # set rcsid {$Id: } source common.tcl if {[llength $argv]>0} { set outputdir [lindex $argv 0] } else { set outputdir "" } header {SQLite Autoincrement} puts { <h1>SQLite Autoincrement</h1> <p> In SQLite, every row of every table has an integer ROWID. The ROWID for each row is unique among all rows in the same table. In SQLite version 2.8 the ROWID is a 32-bit signed integer. Version 3.0 of SQLite expanded the ROWID to be a 64-bit signed integer. </p> <p> You can access the ROWID of an SQLite table using one the special column names ROWID, _ROWID_, or OID. Except if you declare an ordinary table column to use one of those special names, then the use of that name will refer to the declared column not to the internal ROWID. </p> <p> If a table contains a column of type INTEGER PRIMARY KEY, then that column becomes an alias for the ROWID. You can then access the ROWID using any of four different names, the original three names described above or the name given to the INTEGER PRIMARY KEY column. All these names are aliases for one another and work equally well in any context. </p> <p> When a new row is inserted into an SQLite table, the ROWID can either be specified as part of the INSERT statement or it can be assigned automatically by the database engine. To specify a ROWID manually, just include it in the list of values to be inserted. For example: </p> <blockquote><pre> CREATE TABLE test1(a INT, b TEXT); INSERT INTO test1(rowid, a, b) VALUES(123, 5, 'hello'); </pre></blockquote> <p> If no ROWID is specified on the insert, an appropriate ROWID is created automatically. The usual algorithm is to give the newly created row a ROWID that is one larger than the largest ROWID in the table prior to the insert. If the table is initially empty, then a ROWID of 1 is used. If the largest ROWID is equal to the largest possible integer (9223372036854775807 in SQLite version 3.0 and later) then the database engine starts picking candidate ROWIDs at random until it finds one that is not previously used. </p> <p> The normal ROWID selection algorithm described above will generate monotonically increasing unique ROWIDs as long as you never use the maximum ROWID value and you never delete the entry in the table with the largest ROWID. If you ever delete rows or if you ever create a row with the maximum possible ROWID, then ROWIDs from previously deleted rows might be reused when creating new rows and newly created ROWIDs might not be in strictly accending order. </p> <h2>The AUTOINCREMENT Keyword</h2> <p> If a column has the type INTEGER PRIMARY KEY AUTOINCREMENT then a slightly different ROWID selection algorithm is used. The ROWID chosen for the new row is one larger than the largest ROWID that has ever before existed in that same table. If the table has never before contained any data, then a ROWID of 1 is used. If the table has previously held a row with the largest possible ROWID, then new INSERTs are not allowed and any attempt to insert a new row will fail with an SQLITE_FULL error. </p> <p> SQLite keeps track of the largest ROWID that a table has ever held using the special SQLITE_SEQUENCE table. The SQLITE_SEQUENCE table is created and initialized automatically whenever a normal table that contains an AUTOINCREMENT column is created. The content of the SQLITE_SEQUENCE table can be modified using ordinary UPDATE, INSERT, and DELETE statements. But making modifications to this table will likely perturb the AUTOINCREMENT key generation algorithm. Make sure you know what you are doing before you undertake such changes. </p> <p> The behavior implemented by the AUTOINCREMENT keyword is subtly different from the default behavior. With AUTOINCREMENT, rows with automatically selected ROWIDs are guaranteed to have ROWIDs that have never been used before by the same table in the same database. And the automatically generated ROWIDs are guaranteed to be monotonically increasing. These are important properties in certain applications. But if your application does not need these properties, you should probably stay with the default behavior since the use of AUTOINCREMENT requires additional work to be done as each row is inserted and thus causes INSERTs to run a little slower. } footer $rcsid |
Changes to www/lang.tcl.
1 | # | | | | | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | # # Run this Tcl script to generate the lang-*.html files. # set rcsid {$Id: lang.tcl,v 1.80 2004/11/21 01:02:01 drh Exp $} source common.tcl if {[llength $argv]>0} { set outputdir [lindex $argv 0] } else { set outputdir "" } header {Query Language Understood by SQLite} puts { <h1>SQL As Understood By SQLite</h1> <p>The SQLite library understands most of the standard SQL language. But it does <a href="omitted.html">omit some features</a> while at the same time adding a few features of its own. This document attempts to describe precisely what parts of the SQL language SQLite does and does not support. A list of <a href="lang_keywords.html">keywords</a> is also provided.</p> <p>In all of the syntax diagrams that follow, literal text is shown in bold blue. Non-terminal symbols are shown in italic red. Operators that are part of the syntactic markup itself are shown in black roman.</p> <p>This document is just an overview of the SQL syntax implemented by SQLite. Many low-level productions are omitted. For detailed information |
︙ | ︙ | |||
118 119 120 121 122 123 124 | footer_standard $id rename footer "" rename puts "" rename puts_standard puts rename footer_standard footer } set ::section_file [open [file join $outputdir lang_$label.html] w] | | > > | 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 | footer_standard $id rename footer "" rename puts "" rename puts_standard puts rename footer_standard footer } set ::section_file [open [file join $outputdir lang_$label.html] w] header "Query Language Understood by SQLite: $name" puts "<h1>SQL As Understood By SQLite</h1>" puts "<a href=\"lang.html\">\[Contents\]</a>" puts "<h2>$name</h2>" return } } puts "\n<hr />" if {$label!=""} { puts "<a name=\"$label\"></a>" |
︙ | ︙ | |||
444 445 446 447 448 449 450 | <name> [<type>] [[CONSTRAINT <name>] <column-constraint>]* } {type} { <typename> | <typename> ( <number> ) | <typename> ( <number> , <number> ) } {column-constraint} { NOT NULL [ <conflict-clause> ] | | | | 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 | <name> [<type>] [[CONSTRAINT <name>] <column-constraint>]* } {type} { <typename> | <typename> ( <number> ) | <typename> ( <number> , <number> ) } {column-constraint} { NOT NULL [ <conflict-clause> ] | PRIMARY KEY [<sort-order>] [ <conflict-clause> ] [AUTOINCREMENT] | UNIQUE [ <conflict-clause> ] | CHECK ( <expr> ) [ <conflict-clause> ] | DEFAULT <value> | COLLATE <collation-name> } {constraint} { PRIMARY KEY ( <column-list> ) [ <conflict-clause> ] | UNIQUE ( <column-list> ) [ <conflict-clause> ] | |
︙ | ︙ | |||
488 489 490 491 492 493 494 | for the column is executed. If the value is CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP, then the current UTC date and/or time is inserted into the columns. For CURRENT_TIME, the format is HH:MM:SS. For CURRENT_DATE, YYYY-MM-DD. The format for CURRENT_TIMESTAMP is "YYYY-MM-DD HH:MM:SS". </p> <p>Specifying a PRIMARY KEY normally just creates a UNIQUE index | | | > > > > | 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 | for the column is executed. If the value is CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP, then the current UTC date and/or time is inserted into the columns. For CURRENT_TIME, the format is HH:MM:SS. For CURRENT_DATE, YYYY-MM-DD. The format for CURRENT_TIMESTAMP is "YYYY-MM-DD HH:MM:SS". </p> <p>Specifying a PRIMARY KEY normally just creates a UNIQUE index on the corresponding columns. However, if primary key is on a single column that has datatype INTEGER, then that column is used internally as the actual key of the B-Tree for the table. This means that the column may only hold unique integer values. (Except for this one case, SQLite ignores the datatype specification of columns and allows any kind of data to be put in a column regardless of its declared datatype.) If a table does not have an INTEGER PRIMARY KEY column, then the B-Tree key will be a automatically generated integer. The B-Tree key for a row can always be accessed using one of the special names "<b>ROWID</b>", "<b>OID</b>", or "<b>_ROWID_</b>". This is true regardless of whether or not there is an INTEGER PRIMARY KEY. An INTEGER PRIMARY KEY column man also include the keyword AUTOINCREMENT. The AUTOINCREMENT keyword modified the way that B-Tree keys are automatically generated. Additional detail on automatic B-Tree key generation is available <a href="autoinc.html">separately</a>.</p> <p>If the "TEMP" or "TEMPORARY" keyword occurs in between "CREATE" and "TABLE" then the table that is created is only visible to the process that opened the database and is automatically deleted when the database is closed. Any indices created on a temporary table are also temporary. Temporary tables and indices are stored in a separate file distinct from the main database file.</p> |
︙ | ︙ | |||
794 795 796 797 798 799 800 | } puts { <p>The DROP INDEX statement removes an index added with the <a href="#createindex"> CREATE INDEX</a> statement. The index named is completely removed from the disk. The only way to recover the index is to reenter the | | < | 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 | } puts { <p>The DROP INDEX statement removes an index added with the <a href="#createindex"> CREATE INDEX</a> statement. The index named is completely removed from the disk. The only way to recover the index is to reenter the appropriate CREATE INDEX command.</p> <p>The DROP INDEX statement does not reduce the size of the database file. Empty space in the database is retained for later INSERTs. To remove free space in the database, use the <a href="#vacuum">VACUUM</a> command.</p> } |
︙ | ︙ | |||
1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 | command has no effect on an in-memory database.</p> <p>As of SQLite version 3.1, an alternative to using the VACUUM command is auto-vacuum mode, enabled using the <a href="pragma.html#pragma_auto_vacuum">auto_vacuum pragma</a>.</p> } Section {SQLite keywords} keywords puts { | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > < < < < < < < < | < | < < < < < < < < < < < | < | < | | | | < < < < < < < < < < < < | < > > > > > > > > > > > > > > > > > > | | | | < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < > > > > < < < < < < < < < < < < < | | | > > > | > | < | | > > > > | < < < < < < < < < < < < < < < < < < | > | < | < < < < < < < < < < < < < < < < < > > > > > > > > | < < < < < < < < < < < < < < < < > > > > | > | > > > | | | < | | | | | > | > > < | 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 | command has no effect on an in-memory database.</p> <p>As of SQLite version 3.1, an alternative to using the VACUUM command is auto-vacuum mode, enabled using the <a href="pragma.html#pragma_auto_vacuum">auto_vacuum pragma</a>.</p> } # A list of keywords. A asterisk occurs after the keyword if it is on # the fallback list. # set keyword_list [lsort { ABORT* AFTER* ALL ALTER AND AS ASC* ATTACH* AUTOINCREMENT BEFORE* BEGIN* BETWEEN BY CASCADE* CASE CHECK COLLATE COMMIT CONFLICT* CONSTRAINT CREATE CROSS CURRENT_DATE* CURRENT_TIME* CURRENT_TIMESTAMP* DATABASE* DEFAULT DEFERRED* DEFERRABLE DELETE DESC* DETACH* DISTINCT DROP END* EACH* ELSE ESCAPE EXCEPT EXCLUSIVE* EXPLAIN* FAIL* FOR* FOREIGN FROM FULL GLOB* GROUP HAVING IGNORE* IMMEDIATE* IN INDEX INITIALLY* INNER INSERT INSTEAD* INTERSECT INTO IS ISNULL JOIN KEY* LEFT LIKE* LIMIT MATCH* NATURAL NOT NOTNULL NULL OF* OFFSET* ON OR ORDER OUTER PRAGMA* PRIMARY RAISE* REFERENCES REINDEX* RENAME* REPLACE* RESTRICT* RIGHT ROLLBACK ROW* SELECT SET STATEMENT* TABLE TEMP* TEMPORARY* THEN TO TRANSACTION TRIGGER* UNION UNIQUE UPDATE USING VACUUM* VALUES VIEW* WHEN WHERE }] Section {SQLite keywords} keywords puts { <p>The SQL standard specifies a huge number of keywords which may not be used as the names of tables, indices, columns, or databases. The list is so long that few people can remember them all. For most SQL code, your safest bet is to never use any English language word as the name of a user-defined object.</p> <p>If you want to use a keyword as a name, you need to quote it. There are three ways of quoting keywords in SQLite:</p> <p> <blockquote> <table> <tr> <td valign="top"><b>'keyword'</b></td><td width="20"></td> <td>A keyword in single quotes is interpreted as a literal string if it occurs in a context where a string literal is allowed, otherwise it is understood as an identifier.</td></tr> <tr> <td valign="top"><b>"keyword"</b></td><td></td> <td>A keyword in double-quotes is interpreted as an identifier if it matches a known identifier. Otherwise it is interpreted as a string literal.</td></tr> <tr> <td valign="top"><b>[keyword]</b></td><td></td> <td>A keyword enclosed in square brackets is always understood as an identifier. This is not standard SQL. This quoting mechanism is used by MS Access and SQL Server and is included in SQLite for compatibility.</td></tr> </table> </blockquote> </p> <p>Quoted keywords are unaesthetic. To help you avoid them, SQLite allows many keywords to be used unquoted as the names of databases, tables, indices, triggers, views, and/or columns. In the list of keywords that follows, those that can be used as identifiers are shown in an italic font. Keywords that must be quoted in order to be used as identifiers are shown in bold.</p> <p> SQLite adds new keywords from time to time when it take on new features. So to prevent you code from being broken by future enhancements, you should normally quote any indentifier that is an English language word, even if you do not have to. </p> <p> The following are the keywords currently recognized by SQLite: </p> <blockquote> <table width="100%"> <tr> <td align="left" valign="top" width="20%"> } set n [llength $keyword_list] set nCol 5 set nRow [expr {($n+$nCol-1)/$nCol}] set i 0 foreach word $keyword_list { if {[string index $word end]=="*"} { set word [string range $word 0 end-1] set font i } else { set font b } if {$i==$nRow} { puts "</td><td valign=\"top\" align=\"left\" width=\"20%\">" set i 1 } else { incr i } puts "<$font>$word</$font><br>" } puts { </td></tr></table></blockquote> <h2>Special names</h2> <p>The following are not keywords in SQLite, but are used as names of system objects. They can be used as an identifier for a different type of object.</p> <blockquote><b> _ROWID_<br> MAIN<br> OID<br> ROWID<br> SQLITE_MASTER<br> SQLITE_SEQUENCE<br> SQLITE_TEMP_MASTER<br> TEMP<br> </b></blockquote> } footer $rcsid if {[string length $outputdir]} { footer $rcsid } |