The total number of significant digits that a value of the datatype can hold (1.18) Integer numbers defining the index range of an array dimension The condition applied to a CHECK constraint, that will resolve as either true, false or NULL

The name of the column in other_table that is referenced by the foreign keyĪ literal value that is allowed in the given contextĪny context variable whose data type is allowed in the given context

The name of the table referenced by the foreign key constraint May consist of up to 31 characters and must be unique in the table. Name (identifier) for a column in the table. It may consist of up to 31 characters and must be unique in the database.įile specification (only for external tables).įull file name and path, enclosed in single quotes, correct for the local file system and located on a storage device that is physically connected to Firebird’s host computer. 1 CREATE TABLE Statement Parameters Parameter We can check whether the CHECK constraint is the one that LibreOffice puts when faking BOOLEAN.CREATE TABLE tablename ' filespec'] ( EXISTS () | SINGULAR () | () | NOT | OR | AND ::= | != | ^= | ~= | = | | = | ! | ^> | ~> ::= colname ']'] | | | | NULL | NEXT VALUE FOR genname | GEN_ID( genname, ) | CAST( AS ) | () | func(]) > every time we read a SMALLINT (that's the smallest datatype in firebird. > However we could simply read whether there is a CHECK constraint in place in the UI when editing table data directly (because Base > when reading it won't present itself as a boolean, i.e. > as a boolean would also work fine, however there is still the issue that > then, the table has a TINYINT(1) field, not a BOOLEAN field.) > It shouldn't be that hard to fake it at creation time, and reading the field Could we fake BOOLEAN in the driver, if necessary? (Meaning, if (CHECK constraints (and not-nulls) are in RDB$CHECK_CONSTRAINTS, mapping to RDB$TRIGGERS, still need to figure out how to detect this specific check once there though.) However we could simply read whether there is a CHECK constraint in place every time we read a SMALLINT (that's the smallest datatype in firebird - there's no tinyint). in the UI when editing table data directly (because Base thinks it's just an integer). It shouldn't be that hard to fake it at creation time, and reading the field as a boolean would also work fine, however there is still the issue that when reading it won't present itself as a boolean, i.e. > (note: firebird 3 has/will have BOOLEAN datatype) > then, the table has a TINYINT(1) field, not a BOOLEAN field.)

> *creation* time, just map BOOLEAN to TINYINT(1) or something like that.

Maybe we could just do it like MySQL and at table Could be it is a problem with the Bool-field inside of this table.

Firebird constraint limit