4D v16
column_definition
- 4D - SQL Reference
-
- Syntax rules
-
- Syntax rules
- 4d_function_call
- 4d_language_reference
- all_or_any_predicate
- arithmetic_expression
- between_predicate
- case_expression
- column_definition
- column_reference
- command_parameter
- comparison_predicate
- exists_predicate
- foreign_key_definition
- function_call
- in_predicate
- is_null_predicate
- like_predicate
- literal
- predicate
- primary_key_definition
- search_condition
- select_item
- sort_list
- sql_data_type_name
- sql_name
- sql_string
- subquery
- table_constraint
- table_reference
column_definition
|
sql_name sql_data_type_name [(int_number)][NOT NULL [UNIQUE]] [AUTO_INCREMENT] [AUTO_GENERATE] |
||
A column_definition contains the name (sql_name) and data type (sql_data_type_name) of a column. You can also pass an optional int_number as well as the NOT NULL, UNIQUE, AUTO_INCREMENT and/or AUTO_GENERATE keywords.
- Passing NOT NULL in the column_definition means that the column will not accept null values.
- Passing UNIQUE means that the same value may not be inserted into this column twice. Note that only NOT NULL columns can have the UNIQUE attribute. The UNIQUE keyword must always be preceded by NOT NULL.
- Passing AUTO_INCREMENT means that the column will generate a unique number for each new row. This attribute can only be used with number columns.
- Passing AUTO_GENERATE means that a UUID will be generated automatically in the column for each new row. This attribute can only be used with UUID columns.
Each column must have a data type. The column should either be defined as "null" or "not null" and if this value is left blank, the database assumes "null" as the default. The data type for the column does not restrict what data may be put in that column.
Here is a simple example which creates a table with two columns (ID and Name):
CREATE TABLE ACTOR_FANS
(ID INT32, Name VARCHAR NOT NULL UNIQUE);
Produkt: 4D
Thema: Syntax rules
4D - SQL Reference ( 4D v16)
