5.4 TABLE

As a relational DBMS, Firebird stores data in tables. A table is a flat, two-dimensional structure containing any number of rows. Table rows are often called records.

All rows in a table have the same structure and consist of columns. Table columns are often called fields. A table must have at least one column. Each column contains a single type of SQL data.

This section describes how to create, alter and delete tables in a database.

5.4.1 CREATE TABLE

Used forcreating a new table (relation)

Available inDSQL, ESQL

Syntax

1. CREATE [GLOBAL TEMPORARY] TABLE tablename
2. [EXTERNAL [FILE] 'filespec']
3. (<col_def> [, {<col_def> | <tconstraint>} ...])
4. [{<table_attrs> | <gtt_table_attrs>}]

6. <col_def> ::=
7. <regular_col_def>
8. | <computed_col_def>
9. | <identity_col_def>

11. <regular_col_def> ::=
12. colname {<datatype> | domainname}
13. [DEFAULT {<literal> | NULL | <context_var>}]
14. [<col_constraint> ...]
15. [COLLATE collation_name]

17. <computed_col_def> ::=
18. colname [{<datatype> | domainname}]
19. {COMPUTED [BY] | GENERATED ALWAYS AS} (<expression>)

21. <identity_col_def> ::=
22. colname {<datatype> | domainname}
23. GENERATED {ALWAYS | BY DEFAULT} AS IDENTITY
24. [(<identity_col_option>...)]
25. [<col_constraint> ...]

27. <identity_col_option> ::=
28. START WITH start_value
29. | INCREMENT [BY] inc_value

31. <datatype> ::=
32. <scalar_datatype> | <blob_datatype> | <array_datatype>

34. <scalar_datatype> ::=
35. !! See Scalar Data Types Syntax !!

37. <blob_datatype> ::=
38. !! See BLOB Data Types Syntax !!

40. <array_datatype> ::=
41. !! See Array Data Types Syntax !!

43. <col_constraint> ::=
44. [CONSTRAINT constr_name]
45. { PRIMARY KEY [<using_index>]
46. | UNIQUE      [<using_index>]
47. | REFERENCES other_table [(colname)] [<using_index>]
48. [ON DELETE {NO ACTION | CASCADE | SET DEFAULT | SET NULL}]
49. [ON UPDATE {NO ACTION | CASCADE | SET DEFAULT | SET NULL}]
50. | CHECK (<check_condition>)
51. | NOT NULL }

53. <tconstraint> ::=
54. [CONSTRAINT constr_name]
55. { PRIMARY KEY (<col_list>) [<using_index>]
56. | UNIQUE      (<col_list>) [<using_index>]
57. | FOREIGN KEY (<col_list>)
58. REFERENCES other_table [(<col_list>)] [<using_index>]
59. [ON DELETE {NO ACTION | CASCADE | SET DEFAULT | SET NULL}]
60. [ON UPDATE {NO ACTION | CASCADE | SET DEFAULT | SET NULL}]
61. | CHECK (<check_condition>) }

63. <col_list> ::= colname [, colname ...]

65. <using_index> ::= USING
66. [ASC[ENDING] | DESC[ENDING]] INDEX indexname

68. <check_condition> ::=
69. <val> <operator> <val>
70. | <val> [NOT] BETWEEN <val> AND <val>
71. | <val> [NOT] IN (<val> [, <val> ...] | <select_list>)
72. | <val> IS [NOT] NULL
73. | <val> IS [NOT] DISTINCT FROM <val>
74. | <val> [NOT] CONTAINING <val>
75. | <val> [NOT] STARTING [WITH] <val>
76. | <val> [NOT] LIKE <val> [ESCAPE <val>]
77. | <val> [NOT] SIMILAR TO <val> [ESCAPE <val>]
78. | <val> <operator> {ALL | SOME | ANY} (<select_list>)
79. | [NOT] EXISTS (<select_expr>)
80. | [NOT] SINGULAR (<select_expr>)
81. | (<check_condition>)
82. | NOT <check_condition>
83. | <check_condition> OR <check_condition>
84. | <check_condition> AND <check_condition>

86. <operator> ::=
87. <> | != | ^= | ~= | = | < | > | <= | >=
88. | !< | ^< | ~< | !> | ^> | ~>

90. <val> ::=
91. colname ['['array_idx [, array_idx ...]']']
92. | <literal>
93. | <context_var>
94. | <expression>
95. | NULL
96. | NEXT VALUE FOR genname
97. | GEN_ID(genname, <val>)
98. | CAST(<val> AS <cast_type>)
99. | (<select_one>)
100. | func([<val> [, <val> ...]])

102. <cast_type> ::= <domain_or_non_array_type> | <array_datatype>

104. <domain_or_non_array_type> ::=
105. !! See Scalar Data Types Syntax !!

107. <table_attrs> ::= <table_attr> [<table_attr> ...]

109. <table_attr> ::=
110. <sql_security>
111. | {ENABLE | DISABLE} PUBLICATION

113. <sql_security> ::= SQL SECURITY {INVOKER | DEFINER}

115. <gtt_table_attrs> ::= <gtt_table_attr> [gtt_table_attr> ...]

117. <gtt_table_attr> ::=
118. <sql_security>
119. | ON COMMIT {DELETE | PRESERVE} ROWS

Table 5.4.1.1 CREATE TABLE Statement Parameters

The CREATE TABLE statement creates a new table. Any user can create it and its name must be unique among the names of all tables, views and stored procedures in the database.

A table must contain at least one column that is not computed, and the names of columns must be unique in the table.

A column must have either an explicit SQL data type, the name of a domain whose attributes will be copied for the column, or be defined as COMPUTED BY an expression (a calculated field).

A table may have any number of table constraints, including none.

5.4.1.1 Character Columns

You can use the CHARACTER SET clause to specify the character set for the CHAR, VARCHAR and BLOB (text subtype) types. If the character set is not specified, the default character set of the database - at time of the creation of the column - will be used. If the database has no default character set, the NONE character set is applied. In this case, data is stored and retrieved the way it was submitted. Data in any encoding can be added to such a column, but it is not possible to add this data to a column with a different encoding. No transliteration is performed between the source and destination encodings, which may result in errors.

The optional COLLATE clause allows you to specify the collation sequence for character data types, including BLOB SUB_TYPE TEXT. If no collation sequence is specified, the default collation sequence for the specified character set - at time of the creation of the column - is applied.

5.4.1.2 Setting a DEFAULT Value

The optional DEFAULT clause allows you to specify the default value for the table column. This value will be added to the column when an INSERT statement is executed if no value was specified for it and that column was omitted from the INSERT command.

The default value can be a literal of a compatible type, a context variable that is type-compatible with the data type of the column, or NULL, if the column allows it. If no default value is explicitly specified, NULL is implied.

An expression cannot be used as a default value.

5.4.1.3 Domain-based Columns

To define a column, you can use a previously defined domain. If the definition of a column is based on a domain, it may contain a new default value, additional CHECK constraints, and a COLLATE clause that will override the values specified in the domain definition. The definition of such a column may contain additional column constraints (for instance, NOT NULL), if the domain does not have it.

Important

It is not possible to define a domain-based column that is nullable if the domain was defined with the NOT NULL attribute. If you want to have a domain that might be used for defining both nullable and non-nullable columns and variables, it is better practice defining the domain nullable and apply NOT NULL in the downstream column definitions and variable declarations.

5.4.1.4 Identity Columns (Autoincrement)

Identity columns are defined using the GENERATED {ALWAYS | BY DEFAULT} AS IDENTITY clause. The identity column is a column associated with an internal sequence generator. Its value is set automatically every time it is not specified in the INSERT statement, or when the column value is specified as DEFAULT.

Rules

• The data type of an identity column must be an exact number type with zero scale. Allowed types are SMALLINT, INTEGER, BIGINT, NUMERIC(*p*[,0]) and DECIMAL(*p*[,0]) with p <= 18.

• The INT128 type and numeric types with a precision higher than 18 are not supported.

• An identity column cannot have a DEFAULT or COMPUTED value.
• An identity column can be altered to become a regular column.
• A regular column cannot be altered to become an identity column.
• Identity columns are implicitly NOT NULL (non-nullable), and cannot be made nullable.
• Uniqueness is not enforced automatically. A UNIQUE or PRIMARY KEY constraint is required to guarantee uniqueness.
• The use of other methods of generating key values for identity columns, e.g. by trigger-generator code or by allowing users to change or add them, is discouraged to avoid unexpected key violations.
• The INCREMENT value cannot be zero (0).

5.4.1.4.1 GENERATED ALWAYS

An identity column of type GENERATED ALWAYS will always generate a column value on insert. Explicitly inserting a value into a column of this type is not allowed, unless either:

1. the specified value is DEFAULT; this generates the identity value as normal.
2. the OVERRIDING SYSTEM VALUE clause is specified in the INSERT statement; this allows a user value to be inserted.

5.4.1.4.2 GENERATED BY DEFAULT

An identity column of type GENERATED BY DEFAULT will generate a value on insert if no value — other than DEFAULT — is specified on insert. When the OVERRIDING USER VALUE clause is specified in the INSERT statement, the user-provided value is ignored, and an identity value is generated (as if the column was not included in the insert, or the value DEFAULT was specified).

5.4.1.4.3 START WITH Option

The optional START WITH clause allows you to specify an initial value other than 1.

Note

Previous versions of Firebird instead used the specified value as the initial value of the internal generator backing the identity column, so the first value was 1 higher than the START WITH value.

This has been fixed in Firebird 4.0 and now the first value generated is the START WITH value, see also firebird#6615.

5.4.1.4.4 INCREMENT Option

The optional INCREMENT clause allows you to specify another non-zero step value than 1.

Warning

The SQL standard specifies that if INCREMENT is specified with a negative value, and START WITH is not specified, that the first value generated should be the maximum of the column type (e.g. 231 - 1 for INTEGER). Instead, Firebird will start at 1.

5.4.1.5 Calculated Fields

Calculated fields can be defined with the COMPUTED [BY] or GENERATED ALWAYS AS clause (according to the SQL:2003 standard). They mean the same. Describing the data type is not required (but possible) for calculated fields, as the DBMS calculates and stores the appropriate type as a result of the expression analysis. Appropriate operations for the data types included in an expression must be specified precisely.

If the data type is explicitly specified for a calculated field, the calculation result is converted to the specified type. This means, for instance, that the result of a numeric expression could be rendered as a string.

In a query that selects a COMPUTED BY column, the expression is evaluated for each row of the selected data.

Tip

Instead of a computed column, in some cases it makes sense to use a regular column whose value is evaluated in triggers for adding and updating data. It may reduce the performance of inserting/updating records, but it will increase the performance of data selection.

5.4.1.6 Defining an Array Column

• If the column is to be an array, the base type can be any SQL data type except BLOB and array.
• The dimensions of the array are specified between square brackets. (In the Syntax block these brackets appear in quotes to distinguish them from the square brackets that identify optional syntax elements.)

• For each array dimension, one or two integer numbers define the lower and upper boundaries of its index range:

• By default, arrays are 1-based. The lower boundary is implicit and only the upper boundary need be specified. A single number smaller than 1 defines the range num..1 and a number greater than 1 defines the range 1..num.

• Two numbers separated by a colon (:) and optional whitespace, the second greater than the first, can be used to define the range explicitly. One or both boundaries can be less than zero, as long as the upper boundary is greater than the lower.
• When the array has multiple dimensions, the range definitions for each dimension must be separated by commas and optional whitespace.
• Subscripts are validated only if an array actually exists. It means that no error messages regarding invalid subscripts will be returned if selecting a specific element returns nothing or if an array field is NULL.

5.4.1.7 Constraints

Five types of constraints can be specified. They are:

• Primary key (PRIMARY KEY)
• Unique key (UNIQUE)
• Foreign key (REFERENCES)
• CHECK constraint (CHECK)
• NOT NULL constraint (NOT NULL)

Constraints can be specified at column level (column constraints) or at table level (table constraints). Table-level constraints are required when keys (unique constraint, Primary Key, Foreign Key) consist of multiple columns and when a CHECK constraint involves other columns in the row besides the column being defined. The NOT NULL constraint can only be specified as a column constraint. Syntax for some types of constraint may differ slightly according to whether the constraint is defined at the column or table level.

• A column-level constraint is specified during a column definition, after all column attributes except COLLATION are specified, and can involve only the column specified in that definition
• A table-level constraints can only be specified after the definitions of the columns used in the constraint.
• Table-level constraints are a more flexible way to set constraints, since they can cater for constraints involving multiple columns
• You can mix column-level and table-level constraints in the same CREATE TABLE statement

The system automatically creates the corresponding index for a primary key (PRIMARY KEY), a unique key (UNIQUE) and a foreign key (REFERENCES for a column-level constraint, FOREIGN KEY REFERENCES for one at the table level).

5.4.1.7.1 Names for Constraints and Their Indexes

Column-level constraints and their indexes are named automatically:

• The constraint name has the form INTEG_n, where n represents one or more digits
• The index name has the form RDB$PRIMARYn (for a primary key index), RDB$FOREIGNn (for a foreign key index) or RDB$n (for a unique key index). Again, n represents one or more digits.

Automatic naming of table-level constraints and their indexes follows the same pattern, unless the names are supplied explicitly.

5.4.1.7.1.1 Named Constraints

A constraint can be named explicitly if the CONSTRAINT clause is used for its definition. While the CONSTRAINT clause is optional for defining column-level constraints, it is mandatory for table-level constraints. By default, the constraint index will have the same name as the constraint. If a different name is wanted for the constraint index, a USING clause can be included.

5.4.1.7.1.2 The USING Clause

The USING clause allows you to specify a user-defined name for the index that is created automatically and, optionally, to define the direction of the index — either ascending (the default) or descending.

5.4.1.7.2 PRIMARY KEY

The PRIMARY KEY constraint is built on one or more key columns, where each column has the NOT NULL constraint specified. The values across the key columns in any row must be unique. A table can have only one primary key.

• A single-column Primary Key can be defined as a column level or a table-level constraint
• A multi-column Primary Key must be specified as a table-level constraint

5.4.1.7.3 The UNIQUE Constraint

The UNIQUE constraint defines the requirement of content uniqueness for the values in a key throughout the table. A table can contain any number of unique key constraints.

As with the Primary Key, the Unique constraint can be multi-column. If so, it must be specified as a table-level constraint.

5.4.1.7.3.1 NULL in Unique Keys

Firebird’s SQL-99-compliant rules for UNIQUE constraints allow one or more NULLs in a column with a UNIQUE constraint. That makes it possible to define a UNIQUE constraint on a column that does not have the NOT NULL constraint.

For UNIQUE keys that span multiple columns, the logic is a little complicated:

• Multiple rows having null in all the columns of the key are allowed
• Multiple rows having keys with different combinations of nulls and non-null values are allowed
• Multiple rows having the same key columns null and the rest filled with non-null values are allowed, provided the values differ in at least one column
• Multiple rows having the same key columns null and the rest filled with non-null values that are the same in every column will violate the constraint

The rules for uniqueness can be summarised thus:

In principle, all nulls are considered distinct. However, if two rows have exactly the same key columns filled with non-null values, the NULL columns are ignored and the uniqueness is determined on the non-null columns as though they constituted the entire key.

Illustration

1. RECREATE TABLE t( x int, y int, z int, unique(x,y,z));
2. INSERT INTO t values( NULL, 1, 1 );
3. INSERT INTO t values( NULL, NULL, 1 );
4. INSERT INTO t values( NULL, NULL, NULL );
5. INSERT INTO t values( NULL, NULL, NULL ); -- Permitted
6. INSERT INTO t values( NULL, NULL, 1 );    -- Not permitted

5.4.1.7.4 FOREIGN KEY

A Foreign Key ensures that the participating column(s) can contain only values that also exist in the referenced column(s) in the master table. These referenced columns are often called target columns. They must be the primary key or a unique key in the target table. They need not have a NOT NULL constraint defined on them although, if they are the primary key, they will, of course, have that constraint.

The foreign key columns in the referencing table itself do not require a NOT NULL constraint.

A single-column Foreign Key can be defined in the column declaration, using the keyword REFERENCES:

1. ... ,
2. ARTIFACT_ID INTEGER REFERENCES COLLECTION (ARTIFACT_ID),

The column ARTIFACT_ID in the example references a column of the same name in the table COLLECTIONS.

Both single-column and multi-column foreign keys can be defined at the table level. For a multi-column Foreign Key, the table-level declaration is the only option. This method also enables the provision of an optional name for the constraint:

1. ...
2. CONSTRAINT FK_ARTSOURCE FOREIGN KEY(DEALER_ID, COUNTRY)
3. REFERENCES DEALER (DEALER_ID, COUNTRY),

Notice that the column names in the referenced (master) table may differ from those in the Foreign Key.

Note

If no target columns are specified, the Foreign Key automatically references the target table’s Primary Key.

5.4.1.7.4.1 Foreign Key Actions

With the sub-clauses ON UPDATE and ON DELETE it is possible to specify an action to be taken on the affected foreign key column(s) when referenced values in the master table are changed:

NO ACTION

(the default) - Nothing is done

CASCADE

The change in the master table is propagated to the corresponding row(s) in the child table. If a key value changes, the corresponding key in the child records changes to the new value; if the master row is deleted, the child records are deleted.

SET DEFAULT

The Foreign Key columns in the affected rows will be set to their default values as they were when the foreign key constraint was defined.

SET NULL

The Foreign Key columns in the affected rows will be set to NULL.

The specified action, or the default NO ACTION, could cause a Foreign Key column to become invalid. For example, it could get a value that is not present in the master table, or it could become NULL while the column has a NOT NULL constraint. Such conditions will cause the operation on the master table to fail with an error message.

Example

1. ...
2. CONSTRAINT FK_ORDERS_CUST
3. FOREIGN KEY (CUSTOMER) REFERENCES CUSTOMERS (ID)
4. ON UPDATE CASCADE ON DELETE SET NULL

5.4.1.7.5 CHECK Constraint

The CHECK constraint defines the condition the values inserted in this column must satisfy. A condition is a logical expression (also called a predicate) that can return the TRUE, FALSE and UNKNOWN values. A condition is considered satisfied if the predicate returns TRUE or value UNKNOWN (equivalent to NULL). If the predicate returns FALSE, the value will not be accepted. This condition is used for inserting a new row into the table (the INSERT statement) and for updating the existing value of the table column (the UPDATE statement) and also for statements where one of these actions may take place (UPDATE OR INSERT, MERGE).

Important

A CHECK constraint on a domain-based column does not replace an existing CHECK condition on the domain, but becomes an addition to it. The Firebird engine has no way, during definition, to verify that the extra CHECK does not conflict with the existing one.

CHECK constraints — whether defined at table level or column level — refer to table columns by their names. The use of the keyword VALUE as a placeholder — as in domain CHECK constraints — is not valid in the context of defining column constraints.

Examplewith two column-level constraints and one at table-level:

1. CREATE TABLE PLACES (
2. ...
3. LAT DECIMAL(9, 6) CHECK (ABS(LAT) <=  90),
4. LON DECIMAL(9, 6) CHECK (ABS(LON) <= 180),
5. ...
6. CONSTRAINT CHK_POLES CHECK (ABS(LAT) < 90 OR LON = 0)
7. );

5.4.1.7.6 NOT NULL Constraint

In Firebird, columns are nullable by default. The NOT NULL constraint specifies that the column cannot take NULL in place of a value.

A NOT NULL constraint can only be defined as a column constraint, not as a table constraint.

5.4.1.8 SQL SECURITY Clause

The SQL SECURITY clause specifies the security context for executing functions referenced in calculated columns, and check constraints, and the default context used for triggers fired for this table. When SQL Security is not specified, the default value of the database is applied at runtime.

See also SQL Security in chapter Security.

5.4.1.9 Replication Management

When the database has been configured using ALTER DATABASE INCLUDE ALL TO PUBLICATION, new tables will automatically be added for publication, unless overridden using the DISABLE PUBLICATION clause.

If the database has not been configured for INCLUDE ALL (or has later been reconfigured using ALTER DATABASE EXCLUDE ALL FROM PUBLICATION), new tables will not automatically be added for publication. To include tables for publication, the ENABLE PUBLICATION clause must be used.

5.4.1.10 Who Can Create a Table

The CREATE TABLE statement can be executed by:

• Administrators
• Users with the CREATE TABLE privilege

The user executing the CREATE TABLE statement becomes the owner of the table.

5.4.1.11 CREATE TABLE Examples

1. Creating the COUNTRY table with the primary key specified as a column constraint.

1. CREATE TABLE COUNTRY ( 2. COUNTRY COUNTRYNAME NOT NULL PRIMARY KEY, 3. CURRENCY VARCHAR(10) NOT NULL 4. ); 2. Creating the STOCK table with the named primary key specified at the column level and the named unique key specified at the table level.

1. CREATE TABLE STOCK ( 2. MODEL SMALLINT NOT NULL CONSTRAINT PK_STOCK PRIMARY KEY, 3. MODELNAME CHAR(10) NOT NULL, 4. ITEMID INTEGER NOT NULL, 5. CONSTRAINT MOD_UNIQUE UNIQUE (MODELNAME, ITEMID) 6. ); 3. Creating the JOB table with a primary key constraint spanning two columns, a foreign key constraint for the COUNTRY table and a table-level CHECK constraint. The table also contains an array of 5 elements.

1. CREATE TABLE JOB ( 2. JOB_CODE JOBCODE NOT NULL, 3. JOB_GRADE JOBGRADE NOT NULL, 4. JOB_COUNTRY COUNTRYNAME, 5. JOB_TITLE VARCHAR(25) NOT NULL, 6. MIN_SALARY NUMERIC(18, 2) DEFAULT 0 NOT NULL, 7. MAX_SALARY NUMERIC(18, 2) NOT NULL, 8. JOB_REQUIREMENT BLOB SUB_TYPE 1, 9. LANGUAGE_REQ VARCHAR(15) [1:5], 10. PRIMARY KEY (JOB_CODE, JOB_GRADE), 11. FOREIGN KEY (JOB_COUNTRY) REFERENCES COUNTRY (COUNTRY) 12. ON UPDATE CASCADE 13. ON DELETE SET NULL, 14. CONSTRAINT CHK_SALARY CHECK (MIN_SALARY < MAX_SALARY) 15. ); 4. Creating the PROJECT table with primary, foreign and unique key constraints with custom index names specified with the USING clause.

1. CREATE TABLE PROJECT ( 2. PROJ_ID PROJNO NOT NULL, 3. PROJ_NAME VARCHAR(20) NOT NULL UNIQUE USING DESC INDEX IDX_PROJNAME, 4. PROJ_DESC BLOB SUB_TYPE 1, 5. TEAM_LEADER EMPNO, 6. PRODUCT PRODTYPE, 7. CONSTRAINT PK_PROJECT PRIMARY KEY (PROJ_ID) USING INDEX IDX_PROJ_ID, 8. FOREIGN KEY (TEAM_LEADER) REFERENCES EMPLOYEE (EMP_NO) 9. USING INDEX IDX_LEADER 10. ); 5. Creating a table with an identity column

``` 1. create table objects ( 2. id integer generated by default as identity primary key, 3. name varchar(15) 4. );

1. insert into objects (name) values ('Table');
2. insert into objects (id, name) values (10, 'Computer');

3. insert into objects (name) values ('Book');

4. select * from objects order by id;

5. ID NAME

6. ============ ===============
7. 1 Table
8. 2 Book
9. 10 Computer ```
10. Creating the SALARY_HISTORY table with two computed fields. The first one is declared according to the SQL:2003 standard, while the second one is declared according to the traditional declaration of computed fields in Firebird.

1. CREATE TABLE SALARY_HISTORY ( 2. EMP_NO EMPNO NOT NULL, 3. CHANGE_DATE TIMESTAMP DEFAULT 'NOW' NOT NULL, 4. UPDATER_ID VARCHAR(20) NOT NULL, 5. OLD_SALARY SALARY NOT NULL, 6. PERCENT_CHANGE DOUBLE PRECISION DEFAULT 0 NOT NULL, 7. SALARY_CHANGE GENERATED ALWAYS AS 8. (OLD_SALARY * PERCENT_CHANGE / 100), 9. NEW_SALARY COMPUTED BY 10. (OLD_SALARY + OLD_SALARY * PERCENT_CHANGE / 100) 11. ); 7. With DEFINER set for table t, user US needs only the SELECT privilege on t. If it were set for INVOKER, the user would also need the EXECUTE privilege on function f.

``` 1. set term ^; 2. create function f() returns int 3. as 4. begin 5. return 3; 6. end^ 7. set term ;^ 8. create table t (i integer, c computed by (i + f())) SQL SECURITY DEFINER; 9. insert into t values (2); 10. grant select on table t to user us;

1. commit;

2. connect 'localhost:/tmp/7.fdb' user us password 'pas';

3. select * from t; ```
4. With DEFINER set for table tr, user US needs only the INSERT privilege on tr. If it were set for INVOKER, either the user or the trigger would also need the INSERT privilege on table t. The result would be the same if SQL SECURITY DEFINER were specified for trigger tr_ins:

``` 1. create table tr (i integer) SQL SECURITY DEFINER; 2. create table t (i integer); 3. set term ^; 4. create trigger tr_ins for tr after insert 5. as 6. begin 7. insert into t values (NEW.i); 8. end^ 9. set term ;^ 10. grant insert on table tr to user us;

1. commit;

2. connect 'localhost:/tmp/29.fdb' user us password 'pas';

3. insert into tr values(2); ```

5.4.1.12 Global Temporary Tables (GTT)

Global temporary tables have persistent metadata, but their contents are transaction-bound (the default) or connection-bound. Every transaction or connection has its own private instance of a GTT, isolated from all the others. Instances are only created if and when the GTT is referenced. They are destroyed when the transaction ends or on disconnection. The metadata of a GTT can be modified or removed using ALTER TABLE and DROP TABLE, respectively.

Syntax

1. CREATE GLOBAL TEMPORARY TABLE tablename
2. (<column_def> [, {<column_def> | <table_constraint>} ...])
3. [<gtt_table_attrs>]

5. <gtt_table_attrs> ::= <gtt_table_attr> [gtt_table_attr> ...]

7. <gtt_table_attr> ::=
8. <sql_security>
9. | ON COMMIT {DELETE | PRESERVE} ROWS

Syntax notes

• ON COMMIT DELETE ROWS creates a transaction-level GTT (the default), ON COMMIT PRESERVE ROWS a connection-level GTT
• An EXTERNAL [FILE] clause is not allowed in the definition of a global temporary table

GTTs are writable in read-only transactions. The effect is as follows:

Read-only transaction in read-write database

Writable in both ON COMMIT PRESERVE ROWS and ON COMMIT DELETE ROWS

Read-only transaction in read-only database

Writable in ON COMMIT DELETE ROWS only

5.4.1.12.1 Restrictions on GTTs

GTTs can be dressed up with all the features and paraphernalia of ordinary tables (keys, references, indexes, triggers and so on) but there are a few restrictions:

• GTTs and regular tables cannot reference one another
• A connection-bound (PRESERVE ROWS) GTT cannot reference a transaction-bound (DELETE ROWS) GTT
• Domain constraints cannot reference any GTT
• The destruction of a GTT instance at the end of its life cycle does not cause any BEFORE/AFTER delete triggers to fire

Tip

In an existing database, it is not always easy to distinguish a regular table from a GTT, or a transaction-level GTT from a connection-level GTT. Use this query to find out what type of table you are looking at:

1. select t.rdb$type_name
2. from rdb$relations r
3. join rdb$types t on r.rdb$relation_type = t.rdb$type
4. where t.rdb$field_name = 'RDB$RELATION_TYPE'
5. and r.rdb$relation_name = 'TABLENAME'

For an overview of the types of all the relations in the database:

1. select r.rdb$relation_name, t.rdb$type_name
2. from rdb$relations r
3. join rdb$types t on r.rdb$relation_type = t.rdb$type
4. where t.rdb$field_name = 'RDB$RELATION_TYPE'
5. and coalesce (r.rdb$system_flag, 0) = 0

The RDB$TYPE_NAME field will show PERSISTENT for a regular table, VIEW for a view, GLOBAL_TEMPORARY_PRESERVE for a connection-bound GTT and GLOBAL_TEMPORARY_DELETE for a transaction_bound GTT.

5.4.1.12.2 Examples of Global Temporary Tables

1. Creating a connection-scoped global temporary table.

1. CREATE GLOBAL TEMPORARY TABLE MYCONNGTT ( 2. ID INTEGER NOT NULL PRIMARY KEY, 3. TXT VARCHAR(32), 4. TS TIMESTAMP DEFAULT CURRENT_TIMESTAMP) 5. ON COMMIT PRESERVE ROWS; 2. Creating a transaction-scoped global temporary table that uses a foreign key to reference a connection-scoped global temporary table. The ON COMMIT sub-clause is optional because DELETE ROWS is the default.

1. CREATE GLOBAL TEMPORARY TABLE MYTXGTT ( 2. ID INTEGER NOT NULL PRIMARY KEY, 3. PARENT_ID INTEGER NOT NULL REFERENCES MYCONNGTT(ID), 4. TXT VARCHAR(32), 5. TS TIMESTAMP DEFAULT CURRENT_TIMESTAMP 6. ) ON COMMIT DELETE ROWS;

5.4.1.13 External Tables

The optional EXTERNAL [FILE] clause specifies that the table is stored outside the database in an external text file of fixed-length records. The columns of a table stored in an external file can be of any type except BLOB or ARRAY, although for most purposes, only columns of CHAR types would be useful.

All you can do with a table stored in an external file is insert new rows (INSERT) and query the data (SELECT). Updating existing data (UPDATE) and deleting rows (DELETE) are not possible.

A file that is defined as an external table must be located on a storage device that is physically present on the machine where the Firebird server runs and, if the parameter ExternalFileAccess in the firebird.conf configuration file is Restrict, it must be in one of the directories listed there as the argument for Restrict. If the file does not exist yet, Firebird will create it on first access.

Important

The ability to use external files for a table depends on the value set for the ExternalFileAccess parameter in firebird.conf:

• If it is set to None (the default), any attempt to access an external file will be denied.

• The Restrict setting is recommended, for restricting external file access to directories created explicitly for the purpose by the server administrator. For example:

• ExternalFileAccess = Restrict externalfiles will restrict access to a directory named externalfiles directly beneath the Firebird root directory

• ExternalFileAccess = d:\databases\outfiles; e:\infiles will restrict access to just those two directories on the Windows host server. Note that any path that is a network mapping will not work. Paths enclosed in single or double quotes will not work, either.
• If this parameter is set to Full, external files may be accessed anywhere on the host file system. This creates a security vulnerability and is not recommended.

5.4.1.13.1 External File Format

The row format of the external table is fixed length and binary. There are no field delimiters: both field and row boundaries are determined by maximum sizes, in bytes, of the field definitions. It is important to keep this in mind, both when defining the structure of the external table and when designing an input file for an external table that is to import data from another application. The ubiquitous .csv format, for example, is of no use as an input file and cannot be generated directly into an external file.

The most useful data type for the columns of external tables is the fixed-length CHAR type, of suitable lengths for the data they are to carry. Date and number types are easily cast to and from strings whereas, unless the files are to be read by another Firebird database, the native data types — binary data — will appear to external applications as unparseable alphabetti.

Of course, there are ways to manipulate typed data so as to generate output files from Firebird that can be read directly as input files to other applications, using stored procedures, with or without employing external tables. Such techniques are beyond the scope of a language reference. Here, we provide some guidelines and tips for producing and working with simple text files, since the external table feature is often used as an easy way to produce or read transaction-independent logs that can be studied off-line in a text editor or auditing application.

5.4.1.13.1.1 Row Delimiters

Generally, external files are more useful if rows are separated by a delimiter, in the form of a newline sequence that is recognised by reader applications on the intended platform. For most contexts on Windows, it is the two-byte ‘CRLF’ sequence, carriage return (ASCII code decimal 13) and line feed (ASCII code decimal 10). On POSIX, LF on its own is usual; for some MacOSX applications, it may be LFCR. There are various ways to populate this delimiter column. In our example below, it is done by using a BEFORE INSERT trigger and the internal function ASCII_CHAR.

5.4.1.13.1.2 External Table Example

For our example, we will define an external log table that might be used by an exception handler in a stored procedure or trigger. The external table is chosen because the messages from any handled exceptions will be retained in the log, even if the transaction that launched the process is eventually rolled back because of another, unhandled exception. For demonstration purposes, it has just two data columns, a time stamp and a message. The third column stores the row delimiter:

1. CREATE TABLE ext_log
2. EXTERNAL FILE 'd:\externals\log_me.txt' (
3. stamp CHAR (24),
4. message CHAR(100),
5. crlf CHAR(2) -- for a Windows context
6. );
7. COMMIT;

Now, a trigger, to write the timestamp and the row delimiter each time a message is written to the file:

1. SET TERM ^;
2. CREATE TRIGGER bi_ext_log FOR ext_log
3. ACTIVE BEFORE INSERT
4. AS
5. BEGIN
6. IF (new.stamp is NULL) then
7. new.stamp = CAST (CURRENT_TIMESTAMP as CHAR(24));
8. new.crlf = ASCII_CHAR(13) || ASCII_CHAR(10);
9. END ^
10. COMMIT ^
11. SET TERM ;^

Inserting some records (which could have been done by an exception handler or a fan of Shakespeare):

1. insert into ext_log (message)
2. values('Shall I compare thee to a summer''s day?');
3. insert into ext_log (message)
4. values('Thou art more lovely and more temperate');

The output:

1. 2015-10-07 15:19:03.4110Shall I compare thee to a summer's day?
2. 2015-10-07 15:19:58.7600Thou art more lovely and more temperate

5.4.2 ALTER TABLE

Used forAltering the structure of a table.

Available inDSQL, ESQL

Syntax

1. ALTER TABLE tablename
2. <operation> [, <operation> ...]

4. <operation> ::=
5. ADD <col_def>
6. | ADD <tconstraint>
7. | DROP colname
8. | DROP CONSTRAINT constr_name
9. | ALTER [COLUMN] colname <col_mod>
10. | ALTER SQL SECURITY {INVOKER | DEFINER}
11. | DROP SQL SECURITY
12. | {ENABLE | DISABLE} PUBLICATION

14. <col_mod> ::=
15. TO newname
16. | POSITION newpos
17. | <regular_col_mod>
18. | <computed_col_mod>
19. | <identity_col_mod>

21. <regular_col_mod> ::=
22. TYPE {<datatype> | domainname}
23. | SET DEFAULT {<literal> | NULL | <context_var>}
24. | DROP DEFAULT
25. | {SET | DROP} NOT NULL

27. <computed_col_mod> ::=
28. [TYPE <datatype>] {COMPUTED [BY] | GENERATED ALWAYS AS} (<expression>)

30. <identity_col_mod> ::=
31. SET GENERATED {ALWAYS | BY DEFAULT} [<identity_mod_option>...]
32. | <identity_mod_options>...
33. | DROP IDENTITY

35. <identity_mod_options> ::=
36. RESTART [WITH restart_value]
37. | SET INCREMENT [BY] inc_value

39. !! See CREATE TABLE syntax for further rules !!

Table 5.4.2.1 ALTER TABLE Statement Parameters

The ALTER TABLE statement changes the structure of an existing table. With one ALTER TABLE statement it is possible to perform multiple operations, adding/dropping columns and constraints and also altering column specifications.

Multiple operations in an ALTER TABLE statement are separated with commas.

5.4.2.1 Version Count Increments

Some changes in the structure of a table increment the metadata change counter (version count) assigned to every table. The number of metadata changes is limited to 255 for each table, or 32,000 for each view. Once the counter reaches this limit, you will not be able to make any further changes to the structure of the table or view without resetting the counter.

To reset the metadata change counter

You need to back up and restore the database using the gbak utility.

5.4.2.2 The ADD Clause

With the ADD clause you can add a new column or a new table constraint. The syntax for defining the column and the syntax of defining the table constraint correspond with those described for CREATE TABLE statement.

Effect on Version Count

• Each time a new column is added, the metadata change counter is increased by one
• Adding a new table constraint does not increase the metadata change counter

Points to Be Aware of

1. Adding a column with a NOT NULL constraint without a DEFAULT value will fail if the table has existing rows. When adding a non-nullable column, it is recommended either to set a default value for it, or to create it as nullable, update the column in existing rows with a non-null value, and then add a NOT NULL constraint.
2. When a new CHECK constraint is added, existing data is not tested for compliance. Prior testing of existing data against the new CHECK expression is recommended.
3. Although adding an identity column is supported, this will only succeed if the table is empty. Adding an identity column will fail if the table has one or more rows.

5.4.2.3 The DROP Clause

The DROP *colname* clause deletes the specified column from the table. An attempt to drop a column will fail if anything references it. Consider the following items as sources of potential dependencies:

• column or table constraints
• indexes
• stored procedures and triggers
• views

Effect on Version Count

• Each time a column is dropped, the table’s metadata change counter is increased by one.

5.4.2.4 The DROP CONSTRAINT Clause

The DROP CONSTRAINT clause deletes the specified column-level or table-level constraint.

A PRIMARY KEY or UNIQUE key constraint cannot be deleted if it is referenced by a FOREIGN KEY constraint in another table. It will be necessary to drop that FOREIGN KEY constraint before attempting to drop the PRIMARY KEY or UNIQUE key constraint it references.

Effect on Version Count

• Deleting a column constraint or a table constraint does not increase the metadata change counter.

5.4.2.5 The ALTER [COLUMN] Clause

With the ALTER [COLUMN] clause, attributes of existing columns can be modified without the need to drop and re-add the column. Permitted modifications are:

• change the name (does not affect the metadata change counter)
• change the data type (increases the metadata change counter by one)
• change the column position in the column list of the table (does not affect the metadata change counter)
• delete the default column value (does not affect the metadata change counter)
• set a default column value or change the existing default (does not affect the metadata change counter)
• change the type and expression for a computed column (does not affect the metadata change counter)
• set the NOT NULL constraint (does not affect the metadata change counter)
• drop the NOT NULL constraint (does not affec

（本文超出站点单文档体积上限，已截断）