Definition of a database object

Data processing > Database Objects

Attributes tab

Please find below the most important fields.

Field	Description
Code	Identifies the object. For view, function, and procedure objects, the code also corresponds to the name used to create the object in the database
Description	Shows the description of the object in all languages managed by CCH Tagetik.
type	Enables the management of the following database object types: - Functions - Procedure - Query (The definition of a query object may comprise several statements) - View
Order	Indicates the order in which the objects must be executed when the user has selected more than one.

Syntax Tabs

These tabs contain the Mssql, Oracle, Postgres Hana, Other Body syntax management settings, which can be accessed by double-clicking on the database object.

Field	Description
MSSQL body	It contains the instructions defined with a Mssql syntax that will be used in the case of a primary MsSql connection.
Oracle body	It contains the instructions defined with an Oracle syntax that will be used in the case of a primary Oracle connection.
Postgres body	It contains the instructions defined with a Postgres syntax that will be used in the case of a primary connection of Postgres type. If a database object of procedure or function type is being created, both the object name and the parameters must be enclosed in double quotes.
Hana body	It contains the instructions defined with a Hana syntax which will be used in the case of a primary connection of Hana type.
Other Body	Contains the instructions that will be used in case of a connection to a secondary database, using the syntax of the secondary database. IMPORTANT: Instructions can only be defined in the Other Body field for database objects of Query type. If instructions are defined for database objects of type procedure, view, or function, the system returns a validation error upon saving.

IMPORTANT: When creating a database object of type procedure, view, or function, the system checks during saving that the name used in the syntax matches the identifier code of the database object.

IMPORTANT: The instruction is encoded according to the CCH Tagetikstandard before being saved to ensure portability to different databases; chr(13)+chr(10) character combinations are removed from the instruction because they cause malfunctions during deployment. For example, they prevent the use of blank lines or '--' characters when entering comments.

Technical notes on connections¶

Type of connection	Description
Primary connection	Connection defined as primary in the configuration file of the application server standalone.xml.
Secondary connection	Connection defined as secondary in the configuration file of the application server standalone.xml.
Tertiary connection	Schemaless connection defined as primary or secondary in the configuration file of the standalone.xml application server.

IMPORTANT: Secondary connections are marked with prefix (S) and tertiary connections with prefix (T).