Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a problem with the definition of the DEFAULT clause on lang_conflict.html. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
73b4c1e498271d874b5b6a97c262690b |
User & Date: | dan 2010-09-29 18:22:09.000 |
Context
2010-09-30
| ||
16:15 | Added a syntax diagram for numeric literals, especially floating point literals. (check-in: 598ff451ef user: drh tags: trunk) | |
2010-09-29
| ||
18:22 | Fix a problem with the definition of the DEFAULT clause on lang_conflict.html. (check-in: 73b4c1e498 user: dan tags: trunk) | |
11:10 | Change "'CREATE TABLE AS' statements" to "'CREATE TABLE ... AS SELECT ...' statements" on lang_createtable.html. (check-in: 4534ea5789 user: dan tags: trunk) | |
Changes
Changes to pages/lang.in.
︙ | ︙ | |||
695 696 697 698 699 700 701 | rows of data returned by the SELECT statement. ^Rows are assigned contiguously ascending [rowid] values, starting with 1, in the [order by|order] that they are returned by the SELECT statement. <tcl>hd_fragment {tablecoldef} {column definition} {column definitions}</tcl> <h3>Column Definitions</h3> | | | | | > > | 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 | rows of data returned by the SELECT statement. ^Rows are assigned contiguously ascending [rowid] values, starting with 1, in the [order by|order] that they are returned by the SELECT statement. <tcl>hd_fragment {tablecoldef} {column definition} {column definitions}</tcl> <h3>Column Definitions</h3> <p>Unless it is a CREATE TABLE ... AS SELECT statement, a CREATE TABLE includes one or more [column-def|column definitions], optionally followed by a list of [table-constraint|table constraints]. Each column definition consists of the name of the column, optionally followed by the declared type of the column, then one or more optional [column-constraint|column constraints]. Included in the definition of "column constraints" for the purposes of the previous statement are the COLLATE and DEFAULT clauses, even though these are not really constraints in the sense that they do not restrict the data that the table may contain. The other constraints - NOT NULL, CHECK, UNIQUE, PRIMARY KEY and FOREIGN KEY constraints - impose restrictions on the tables data, and are are described under [constraints|SQL Data Constraints] below. <p>^Unlike most SQL databases, SQLite does not restrict the type of data that may be inserted into a column based on the columns declared type. Instead, SQLite uses [dynamic typing]. ^The declared type of a column is used to determine the [affinity] of the column only. <p>The DEFAULT clause specifies a default value to use for the column if no value is explicitly provided by the user when doing an [INSERT]. ^If there is no explicit DEFAULT clause attached to a column definition, then the default value of the column is NULL. ^(An explicit DEFAULT clause may specify that the default value is NULL, a string constant, a blob constant, a signed-number, or any constant expression enclosed in parentheses. An explicit default value may also be one of the special case-independent keywords CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP.)^ ^For the purposes of the DEFAULT clause, an expression is considered constant provided that it does not contain any sub-queries or string constants enclosed in double quotes. <p>^(Each time a row is inserted into the table by an INSERT statement that does not provide explicit values for all table columns the values stored in the new row are determined by their default values)^, as follows: <ul> <li><p>^If the default value of the column is a constant NULL, text, blob or |
︙ | ︙ |