[
https://issues.apache.org/jira/browse/TRAFODION-3255?focusedWorklogId=185631&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-185631
]
ASF GitHub Bot logged work on TRAFODION-3255:
---------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jan/19 08:04
Start Date: 16/Jan/19 08:04
Worklog Time Spent: 10m
Work Description: liuyu000 commented on pull request #1768:
[TRAFODION-3255] Add *ALTER TABLE ... ADD PRIMARY KEY* in *Trafodion SQL
Reference Manual*
URL: https://github.com/apache/trafodion/pull/1768#discussion_r248181593
##########
File path: docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc
##########
@@ -490,98 +491,107 @@ For any row that you add after the column is added, if
no value is specified for
receives a default value based on the current timestamp at the time the row is
added.
<<<
-** `[[constraint _constraint-name_] _column-constraint_]`
+** `[[CONSTRAINT _constraint-name_] _column-constraint_]`
+
specifies a name for the column or table constraint. _constraint-name_ must
have the same schema as _table_ and must be
-unique among constraint names in its schema. if you omit the schema portions
of the name you specify in _constraint-name_,
-trafodion sql expands the constraint name by using the schema for _table_. see
<<database_object_names,database object names>>.
+unique among constraint names in its schema. If you omit the schema portions
of the name you specify in _constraint-name_,
+trafodion sql expands the constraint name by using the schema for _table_. See
<<database_object_names,database object names>>.
+
if you do not specify a constraint name, trafodion sql constructs an sql
identifier as the name for the constraint in the schema
-for _table._ the identifier consists of the fully qualified table name
concatenated with a system-generated unique identifier.
+for _table._ The identifier consists of the fully qualified table name
concatenated with a system-generated unique identifier.
for example, a constraint on table a.b.c might be assigned a name such as
a.b.c_123…_01….
*** `_column-constraint_` options:
-**** `not null`
+**** `NOT NULL`
+
-is a column constraint that specifies that the column cannot contain nulls. if
you omit not null, nulls are allowed in the column.
-if you specify both not null and no default, then each row inserted in the
table must include a value for the column. see <<null,null>>.
+is a column constraint that specifies that the column cannot contain nulls. If
you omit not null, nulls are allowed in the column.
+If you specify both not null and no default, then each row inserted in the
table must include a value for the column. See <<null,null>>.
-**** `unique`
+**** `UNIQUE`
++
+is a column constraint that specifies that the column cannot contain more than
one occurrence of the same value. If you omit unique,
+duplicate values are allowed unless the column is part of the primary key.
Columns that you define as unique must be specified as not null.
+
+**** `PRIMARY KEY [ASC[ENDING] | DESC[ENDING]]`
++
+is a column constraint that specifies a column as the primary key for the
table.
+
-is a column constraint that specifies that the column cannot contain more than
one occurrence of the same value. if you omit unique,
-duplicate values are allowed unless the column is part of the primary key.
columns that you define as unique must be specified as not null.
+ASCENDING and DESCENDING specify the direction for entries in one column
within the key. The default is ASCENDING.
++
+The PRIMARY KEY value in each row of the table must be unique within the
table. You can specify PRIMARY KEY only once on any CREATE TABLE statement.
++
+Trafodion SQL uses the primary key as the clustering key of the table to avoid
creating a separate, unique index to implement
+the primary key constraint.
-**** `check (_condition_)`
+**** `CHECK (_condition_)`
+
is a constraint that specifies a condition that must be satisfied for each row
in the table. see <<search_condition,search condition>>.
you cannot refer to the current_date, current_time, or current_timestamp
function in a check constraint, and you cannot use
subqueries in a check constraint.
<<<
-**** `references _ref-spec_`
+**** `REFERENCES _ref-spec_`
+
-specifies a references column constraint. the maximum combined length of the
columns for a references constraint is 2048 bytes. +
+specifies a references column constraint. The maximum combined length of the
columns for a references constraint is 2048 bytes. +
***** `_ref-spec_` is:
+
`_referenced-table_ [(_column-list_)]`
+
-`_referenced-table_` is the table referenced by the foreign key in a
referential constraint. _referenced-table_ cannot be a view.
+****** `_referenced-table_` is the table referenced by the foreign key in a
referential constraint. _referenced-table_ cannot be a view.
_referenced-table_ cannot be the same as _table_. _referenced-table_
corresponds to the foreign key in the _table_.
+
-`_column-list_` specifies the column or set of columns in the
_referenced-table_ that corresponds to the foreign key in _table_. the
+****** `_column-list_` specifies the column or set of columns in the
_referenced-table_ that corresponds to the foreign key in _table_. the
columns in the column list associated with references must be in the same
order as the columns in the column list associated with foreign
key. if _column-list_ is omitted, the referenced table's primary key columns
are the referenced columns.
+
a table can have an unlimited number of referential constraints, and you can
specify the same foreign key in more than one referential
constraint, but you must define each referential constraint separately. you
cannot create self-referencing foreign key constraints.
-* `add [constraint _constraint-name_] _table-constraint_`
+
+* `ADD [constraint _constraint-name_] _table-constraint_`
+
adds a constraint to the table and optionally specifies _constraint-name_ as
the name for the constraint. the new constraint
must be consistent with any data already present in the table.
<<<
-** `constraint _constraint-name_`
+** `CONSTRAINT _constraint-name_`
+
specifies a name for the column or table constraint. _constraint-name_ must
have the same schema as _table_ and must be unique among constraint
-names in its schema. if you omit the schema portions of the name you specify
in _constraint-name_, trafodion sql expands the constraint
-name by using the schema for table. see <<database_object_names,database
object names>>.
+names in its schema. If you omit the schema portions of the name you specify
in _constraint-name_, trafodion sql expands the constraint
+name by using the schema for table. See <<database_object_names,database
object names>>.
+
-if you do not specify a constraint name, trafodion sql constructs an sql
identifier as the name for the constraint in the schema for table. the
-identifier consists of the fully qualified table name concatenated with a
system-generated unique identifier. for example, a constraint on table
+if you do not specify a constraint name, trafodion sql constructs an sql
identifier as the name for the constraint in the schema for table. The
+identifier consists of the fully qualified table name concatenated with a
system-generated unique identifier. For example, a constraint on table
a.b.c might be assigned a name such as a.b.c_123…_01….
+
** `_table-constraint_` options:
-*** `unique (_column-list_)`
+*** `UNIQUE (_column-list_)`
+
is a table constraint that specifies that the column or set of columns cannot
contain more
than one occurrence of the same value or set of values.
+
-`_column-list_` cannot include more than one occurrence of the same column. in
addition, the set of columns that you specify on a unique
+**** `_column-list_` cannot include more than one occurrence of the same
column. in addition, the set of columns that you specify on a unique
Review comment:
Oops, thanks Dave, I've corrected 😁
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 185631)
Time Spent: 1h 10m (was: 1h)
> Add *ALTER TABLE ... ADD PRIMARY KEY* in *Trafodion SQL Reference Manual*
> -------------------------------------------------------------------------
>
> Key: TRAFODION-3255
> URL: https://issues.apache.org/jira/browse/TRAFODION-3255
> Project: Apache Trafodion
> Issue Type: Documentation
> Reporter: Liu Yu
> Assignee: Liu Yu
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
