RDB$LOG_FILES
RDB$LOG_FILES
is not currently used.
RDB$LOG_FILES
RDB$LOG_FILES
is not currently used.
RDB$PACKAGES
RDB$PACKAGES
stores the definition (header and body) of SQL packages.
Column Name | Data Type | Description |
---|---|---|
|
|
Name of the package |
|
|
The PSQL sourcecode of the package header |
|
|
The PSQL sourcecode of the package body |
|
|
Indicates whether the body of the package is still valid. |
|
|
May reference a security class defined in the table |
|
|
The username of the user who created the package originally |
|
|
Flag:
|
|
|
Optional description of the package (comment) |
|
|
The
|
RDB$PAGES
RDB$PAGES
stores and maintains information about database pages and their usage.
Column Name | Data Type | Description |
---|---|---|
|
|
The unique number of a physically created database page |
|
|
The identifier of the table to which the page is allocated |
|
|
The number of the page in the sequence of all pages allocated to this table |
|
|
Indicates the page type (data, index, |
RDB$PROCEDURES
RDB$PROCEDURES
stores the definitions of stored procedures, including their PSQL source code and its binary language representation (BLR).The next table, RDB$PROCEDURE_PARAMETERS
, stores the definitions of input and output parameters.
Column Name | Data Type | Description |
---|---|---|
|
|
Stored procedure name (identifier) |
|
|
The procedure’s unique, system-generated identifier |
|
|
Indicates the number of input parameters. |
|
|
Indicates the number of output parameters. |
|
|
Any text comments related to the procedure |
|
|
The PSQL source code of the procedure |
|
|
The binary language representation (BLR) of the procedure code (PSQL procedures only) |
|
|
May point to the security class defined in the system table |
|
|
The username of the procedure’s Owner — the user who was |
|
|
A metadata description of the procedure, used internally for optimization |
|
|
Indicates whether the procedure is defined by a user (value 0) or by the system (a value of 1 or greater) |
|
|
Procedure type:
* for procedures created before Firebird 1.5 |
|
|
Indicates whether the source PSQL of the stored procedure remains valid after the latest |
|
|
Contains debugging information about variables used in the stored procedure |
|
|
Engine for external functions. |
|
|
The exported name of the external function in the procedure library.Note, this is often not the same as |
|
|
Package name of the procedure (or |
|
|
|
|
|
The
|
RDB$PROCEDURE_PARAMETERS
RDB$PROCEDURE_PARAMETERS
stores the parameters of stored procedures and their attributes.It holds one row for each parameter.
Column Name | Data Type | Description |
---|---|---|
|
|
Parameter name |
|
|
The name of the procedure where the parameter is defined |
|
|
The sequential number of the parameter |
|
|
Indicates whether the parameter is for input (value 0) or output (value 1) |
|
|
The name of the user-created domain, when a domain is referenced instead of a data type.If the name starts with the prefix “RDB$”, it is the name of the domain automatically generated by the system for the parameter. |
|
|
Could store comments related to the parameter |
|
|
Indicates whether the parameter was defined by the system (value or greater) or by a user (value 0) |
|
|
The binary language representation (BLR) of the default value of the parameter |
|
|
The default value for the parameter, in PSQL code |
|
|
The identifier of the collation used for a character parameter |
|
|
The flag indicating whether |
|
|
Flag: indicates how this parameter is passed:
|
|
|
The name of the column the parameter references, if it was declared using |
|
|
The name of the table the parameter references, if it was declared using |
|
|
Package name of the procedure (or |
RDB$PUBLICATIONS
RDB$PUBLICATIONS
stores the replication publications defined in the database.
Column Name | Data Type | Description |
---|---|---|
|
|
Publication name |
|
|
The username of the user who created the publication |
|
|
Flag:
|
|
|
Inactive ( |
|
|
Automatically add new tables to publication:
|
Note
|
In Firebird 5.0 there is a single (pre-defined) publication named |
RDB$PUBLICATION_TABLES
RDB$PUBLICATION_TABLES
stores the names of tables that are replicated as part of a publication.
Column Name | Data Type | Description |
---|---|---|
|
|
Publication name |
|
|
Table name |
RDB$REF_CONSTRAINTS
RDB$REF_CONSTRAINTS
stores the attributes of the referential constraints — Foreign Key relationships and referential actions.
Column Name | Data Type | Description |
---|---|---|
|
|
Foreign key constraint name, defined by the user or automatically generated by the system |
|
|
The name of the primary or unique key constraint linked by the |
|
|
Not used.The current value is |
|
|
Referential integrity actions applied to the foreign key record(s) when the primary (unique) key of the parent table is updated: |
|
|
Referential integrity actions applied to the foreign key record(s) when the primary (unique) key of the parent table is deleted: |
RDB$CHARACTER_SETS
RDB$CHARACTER_SETS
names and describes the character sets available in the database.
Column Name | Data Type | Description |
---|---|---|
|
|
Character set name |
|
|
Not used |
|
|
The number of characters in the set.Not used for existing character sets |
|
|
The name of the default collation for the character set |
|
|
Unique character set identifier |
|
|
System flag: value is 1 if the character set is defined in the system when the database is created;value is 0 for a user-defined character set |
|
|
Could store text description of the character set |
|
|
For a user-defined character set that is accessed via an external function, the name of the external function |
|
|
The maximum number of bytes representing one character |
|
|
May reference a security class defined in the table |
|
|
The username of the user who created the character set originally |
RDB$RELATIONS
RDB$RELATIONS
stores the top-level definitions and attributes of all tables and views in the system.
Column Name | Data Type | Description |
---|---|---|
|
|
The binary language representation (BLR) of the query specification of a view.The field stores |
|
|
Contains the original source text of the query for a view, in SQL language.User comments are included.The field stores |
|
|
Could store comments related to the table or view |
|
|
Internal identifier of the table or view |
|
|
indicates whether the table or view is user-defined (value 0) or system-defined (value 1 or greater) |
|
|
The total length of the database key.For a table: 8 bytes.For a view, the length is 8 multiplied by the number of tables referenced by the view |
|
|
Internal use, points to the relation’s record in |
|
|
The field ID for the next column to be added.The number is not decremented when a column is dropped. |
|
|
Table or view name |
|
|
May reference a security class defined in the table |
|
|
The full path to the external data file if the table is defined with the |
|
|
Table metadata description, used internally for optimization |
|
|
Could store comments related to the external file of an external table |
|
|
The username of the user who created the table or view originally |
|
|
Default security class, used when a new column is added to the table |
|
|
Internal flags |
|
|
The type of the relation object being described:
|
|
|
The
|
RDB$RELATION_CONSTRAINTS
RDB$RELATION_CONSTRAINTS
stores the definitions of all table-level constraints: primary, unique, foreign key, CHECK
, NOT NULL
constraints.
Column Name | Data Type | Description |
---|---|---|
|
|
The name of the table-level constraint defined by the user, or otherwise automatically generated by the system |
|
|
The name of the constraint type: |
|
|
The name of the table this constraint applies to |
|
|
Currently |
|
|
Currently |
|
|
The name of the index that supports this constraint.For a |
RDB$RELATION_FIELDS
RDB$RELATION_FIELDS
stores the definitions of table and view columns.
Column Name | Data Type | Description |
---|---|---|
|
|
Column name |
|
|
The name of the table or view that the column belongs to |
|
|
Domain name on which the column is based, either a user-defined one specified in the table definition or one created automatically by the system using the set of attributes defined.The attributes are in the table |
|
|
Not currently used |
|
|
Only populated for a view, it is the name of the column from the base table |
|
|
Not used |
|
|
The zero-based ordinal position of the column in the table or view, numbering from left to right |
|
|
Not used |
|
|
Indicates whether the column is a regular one (value 1) or a computed one (value 0) |
|
|
An ID assigned from |
|
|
For a view column, the internal identifier of the base table from which this field derives |
|
|
Comments related to the table or view column |
|
|
The binary language representation (BLR) of the default value of the column |
|
|
Indicates whether the column is user-defined (value 0) or system-defined (value 1 or greater) |
|
|
May reference a security class defined in |
|
|
Not used |
|
|
Indicates whether the column is nullable ( |
|
|
The source text of the |
|
|
The identifier of the collation in the character set for the column, if it is not the default collation |
|
|
Internal generator name for generating an identity value for the column. |
|
|
The identity type of the column
|
RDB$ROLES
RDB$ROLES
stores the roles that have been defined in this database.
Column Name | Data Type | Description |
---|---|---|
|
|
Role name |
|
|
The username of the role owner |
|
|
Could store comments related to the role |
|
|
System flag |
|
|
May reference a security class defined in the table |
|
|
Bitset with the system privileges granted to a role, with the following bits 0 - unused |
RDB$SECURITY_CLASSES
RDB$SECURITY_CLASSES
stores the access control lists
Column Name | Data Type | Description |
---|---|---|
|
|
Security class name |
|
|
The access control list related to the security class.It enumerates users and their privileges |
|
|
Could store comments related to the security class |
RDB$TIME_ZONES
RDB$TIME_ZONES
lists the named time zones supported by the engine.It is a virtual table that is populated using the current time zone database of the Firebird engine.
Column Name | Data Type | Description |
---|---|---|
|
|
The unique identifier of the time zone as used by Firebird.For example, this identifier is used in the |
|
|
Name of the time zone as specified by the time zone database |
RDB$TRANSACTIONS
RDB$TRANSACTIONS
stores the states of distributed transactions and other transactions that were prepared for two-phase commit with an explicit prepare message.
Column Name | Data Type | Description |
---|---|---|
|
|
The unique identifier of the transaction being tracked |
|
|
Transaction state:
|
|
|
Not used |
|
|
Describes the prepared transaction and could be a custom message supplied to |
RDB$TRIGGERS
RDB$TRIGGERS
stores the trigger definitions for all tables and views.
Column Name | Data Type | Description |
---|---|---|
|
|
Trigger name |
|
|
The name of the table or view the trigger applies to.NULL if the trigger is applicable to a database event (“database trigger”) |
|
|
Position of this trigger in the sequence.Zero usually means that no sequence position is specified |
|
|
The event the trigger fires on, see [fblangref-appx04-triggers-type] |
|
|
Stores the source code of the trigger in PSQL |
|
|
The binary language representation (BLR) of the trigger code (PSQL trigger only) |
|
|
Trigger comment text |
|
|
Indicates whether the trigger is currently inactive (1) or active (0) |
|
|
Flag: indicates whether the trigger is user-defined (value 0) or system-defined (value 1 or greater) |
|
|
Internal use |
|
|
Indicates whether the text of the trigger remains valid after the latest modification by the |
|
|
Contains debugging information about variables used in the trigger |
|
|
Engine for external triggers. |
|
|
The exported name of the external trigger in the trigger library.Note, this is often not the same as |
|
|
The
|
RDB$TRIGGER_TYPE
ValueThe value of RDB$TRIGGER_TYPE
is built from:
1
|
before insert |
2
|
after insert |
3
|
before update |
4
|
after update |
5
|
before delete |
6
|
after delete |
17
|
before insert or update |
18
|
after insert or update |
25
|
before insert or delete |
26
|
after insert or delete |
27
|
before update or delete |
28
|
after update or delete |
113
|
before insert or update or delete |
114
|
after insert or update or delete |
8192
|
on connect |
8193
|
on disconnect |
8194
|
on transaction start |
8195
|
on transaction commit |
8196
|
on transaction rollback |
Note
|
Identification of the exact |
For DDL triggers, the trigger type is obtained by bitwise OR above the event phase (0
— BEFORE, 1
— AFTER) and all listed types events:
0x0000000000004002
|
|
0x0000000000004004
|
|
0x0000000000004008
|
|
0x0000000000004010
|
|
0x0000000000004020
|
|
0x0000000000004040
|
|
0x0000000000004080
|
|
0x0000000000004100
|
|
0x0000000000004200
|
|
0x0000000000004400
|
|
0x0000000000004800
|
|
0x0000000000005000
|
|
0x0000000000014000
|
|
0x0000000000024000
|
|
0x0000000000044000
|
|
0x0000000000084000
|
|
0x0000000000104000
|
|
0x0000000000204000
|
|
0x0000000000404000
|
|
0x0000000000804000
|
|
0x0000000001004000
|
|
0x0000000002004000
|
|
0x0000000004004000
|
|
0x0000000008004000
|
|
0x0000000010004000
|
|
0x0000000020004000
|
|
0x0000000040004000
|
|
0x0000000080004000
|
|
0x0000000100004000
|
|
0x0000000200004000
|
|
0x0000000400004000
|
|
0x0000000800004000
|
|
0x0000001000004000
|
|
0x0000002000004000
|
|
0x0000004000004000
|
|
0x0000008000004000
|
|
0x0000010000004000
|
|
0x0000020000004000
|
|
0x0000040000004000
|
|
0x0000080000004000
|
|
0x0000100000004000
|
|
0x0000200000004000
|
|
0x0000400000004000
|
|
0x0000800000004000
|
|
0x7FFFFFFFFFFFDFFE
|
|
For example a trigger withBEFORE CREATE PROCEDURE OR CREATE FUNCTION
will be of type 0x0000000000004090
,AFTER CREATE PROCEDURE OR CREATE FUNCTION
— 0x0000000000004091
,BEFORE DROP FUNCTION OR DROP EXCEPTION
— 0x00000000000044200
,AFTER DROP FUNCTION OR DROP EXCEPTION
— 0x00000000000044201
,BEFORE DROP TRIGGER OR DROP DOMAIN
— 0x00000000001005000
,AFTER DROP TRIGGER OR DROP DOMAIN
— 0x00000000001005001
.
RDB$TRIGGER_MESSAGES
RDB$TRIGGER_MESSAGES
stores the trigger messages.
Column Name | Data Type | Description |
---|---|---|
|
|
The name of the trigger the message is associated with |
|
|
The number of the message within this trigger (from 1 to 32,767) |
|
|
Text of the trigger message |
RDB$TYPES
RDB$TYPES
stores the defining sets of enumerated types used throughout the system.
Column Name | Data Type | Description |
---|---|---|
|
|
Enumerated type name.Each type name masters its own set of types, e.g., object types, data types, character sets, trigger types, blob subtypes, etc. |
|
|
The object type identifier.A unique series of numbers is used within each separate enumerated type.For example, for the
|
|
|
The name of a member of an enumerated type, e.g., TABLE, VIEW, TRIGGER, etc. in the example above.In the |
|
|
Any text comments related to the enumerated type |
|
|
Flag: indicates whether the type-member is user-defined (value 0) or system-defined (value 1 or greater) |
RDB$CHECK_CONSTRAINTS
RDB$CHECK_CONSTRAINTS
provides the cross references between the names of system-generated triggers for constraints and the names of the associated constraints (NOT NULL
constraints, CHECK
constraints and the ON UPDATE
and ON DELETE
clauses in foreign key constraints).
Column Name | Data Type | Description |
---|---|---|
|
|
Constraint name, defined by the user or automatically generated by the system |
|
|
For a |
RDB$USER_PRIVILEGES
RDB$USER_PRIVILEGES
stores the SQL access privileges for Firebird users and privileged objects.
Column Name | Data Type | Description |
---|---|---|
|
|
The user or object that is granted this privilege |
|
|
The user who grants the privilege |
|
|
The privilege granted hereby:
|
|
|
Whether the WITH GRANT OPTION authority is included with the privilege:
|
|
|
The name of the object (table, view, procedure or role) the privilege is granted ON |
|
|
The name of the column the privilege is applicable to, for a column-level privilege (an |
|
|
Identifies the type of user the privilege is granted TO (a user, a procedure, a view, etc.) |
|
|
Identifies the type of the object the privilege is granted ON
|
RDB$VIEW_RELATIONS
RDB$VIEW_RELATIONS
stores the tables that are referred to in view definitions.There is one record for each table in a view.
Column Name | Data Type | Description |
---|---|---|
|
|
View name |
|
|
The name of the table, view or stored procedure the view references |
|
|
The alias used to reference the view column in the BLR code of the query definition |
|
|
The text associated with the alias reported in the |
|
|
Context type:
|
|
|
Package name for a stored procedure in a package |
RDB$COLLATIONS
RDB$COLLATIONS
stores collations for all character sets.
Column Name | Data Type | Description |
---|---|---|
|
|
Collation name |
|
|
Collation identifier.Together with the character set identifier, it is a unique collation identifier |
|
|
Character set identifier.Together with the collection sequence identifier, it is a unique identifier |
|
|
Collation attributes.It is a bit mask where the first bit shows whether trailing spaces should be taken into account in collations (0 - NO PAD; 1 - PAD SPACE);the second bit shows whether the collation is case-sensitive (0 - CASE SENSITIVE, 1 - CASE INSENSITIVE);the third bit shows whether the collation is accent-sensitive (0 - ACCENT SENSITIVE, 1 - ACCENT SENSITIVE).Thus, the value of 5 means that the collation does not take into account trailing spaces and is accent-insensitive |
|
|
Flag: the value of 0 means it is user-defined;the value of 1 means it is system-defined |
|
|
Could store text description of the collation |
|
|
Not currently used |
|
|
The name of the base collation for this collation |
|
|
Describes specific attributes |
|
|
May reference a security class defined in the table |
|
|
The username of the user who created the collation originally |
RDB$CONFIG
RDB$CONFIG
is a virtual table showing the configuration settings of the current database for the current connection.
Table RDB$CONFIG
is populated from in-memory structures upon request and its instance is preserved for the SQL query lifetime.For security reasons, access to this table is allowed for administrators only.Non-privileged users see no rows in this table (and no error is raised).
Column Name | Data Type | Description |
---|---|---|
|
|
Unique row identifier, no special meaning |
|
|
Setting name (e.g. |
|
|
Actual value of setting |
|
|
Default value of setting (defined in the Firebird code) |
|
|
TRUE if value is explicitly configured, FALSE when default |
|
|
Name of the configuration file (relative to the Firebird root directory) where this setting was taken from, or special value |
RDB$DATABASE
RDB$DATABASE
stores basic information about the database.It contains only one record.
Column Name | Data Type | Description |
---|---|---|
|
|
Database comment text |
|
|
A number that steps up by one each time a table or view is added to the database |
|
|
The security class defined in |
|
|
The name of the default character set for the database set in the |
|
|
Number of seconds "delay" (established with the |
|
|
The default
|
RDB$DB_CREATORS
RDB$DB_CREATORS
contains a list of users granted the CREATE DATABASE
privilege when using the specified database as a security database.
Column Name | Data Type | Description |
---|---|---|
|
|
User or role name |
|
|
Type of user
|
RDB$DEPENDENCIES
RDB$DEPENDENCIES
stores the dependencies between database objects.
Column Name | Data Type | Description |
---|---|---|
|
|
The name of the view, procedure, trigger, |
|
|
The name of the object that the defined object — the table, view, procedure, trigger, |
|
|
The column name in the depended-on object that is referred to by the dependent view, procedure, trigger, |
|
|
Identifies the type of the dependent object:
|
|
|
Identifies the type of the object depended on:
|
|
|
The package of a procedure or function for which this describes the dependency. |