Glossary

• Record Complex - a type of Omnidex Domain where child records are collectively indexed together with the parent record.

• A child table which is indexed with only primary keys (from parent table). See Record Complex.

• Relational Database Management System; a database approach involving two-dimensional tables to define data relationships.

• A set of field, or column, values in a data file or database table; (2) a structured collection of information or data treated as a unit; also known as a row or tuple.

• When a child table is prejoined (linked) to a parent table,

an affiliation of records in an SI domain that all contain the same OMNIDEX SI value; for example, qualifying from child or parent returns parent rows; keys that qualify record complexes (MDK Indexes in parent tables or master data sets, and MDK Indexes installed with the Record Complex option). When Record Complex is installed on a keyword index in a child table, the index is treated as if it belonged to the parent table. See SI domain, Record Specific, RC child, RS child.

• A value that uniquely identifies a record in a table;
• A search item (SI) for a parent table and a row ID for all other tables.

• An internally maintained value associated with the position in a detail file of individual detail records.

• A type of Omnidex Domain that indexes child records individually instead of collectively.

• An affiliation of records in an SI domain that are indexed in reference to their own table; for example, if qualifying records from a child table, query will return child rows with the ability to access the parent rows, else if qualifying from the parent table, query will return parent rows;

refers to MDK Index or keyword retrievals that qualify individual detail records. Non-Record Complex keys in detail records are Record Specific. See Record Complex and SI domain.

• A portion of an OMNIDEX index that correlates each parent constraint with the corresponding child row IDs. This portion of the index is used for performing qualifications, as well as several types of joins.

• Row IDs subject to OMNIDEX manipulation to insure sequential nature. See well-behaved row IDs.

• A method of ensuring that the relationship between records in related tables is maintained. Specifically, referential integrity checks to make sure that a parent record exists for every child record.

• The greater than (>), greater than or equal to (>, less than (<), less than or equal to (⇐), and equal ( operators used to specify a relational retrieval.

relative record number

• See also record number.

• See child key.

• The process of replacing ID values in the kernel aggregate results with the column specified in the group by the statement. The ID value is used to read into the dimension or snowflake table where the Group By column resides.

• Intrinsics that are used to search for or retrieve records.

• An outer join in which all rows from the right table in the JOIN clause are included, only rows from the left table with matching rows in the right table are included, and right table rows with no matching left table rows are matched with nulls.

When Omnidex encounters a right outer join, it will attempt to convert it to a left outer join by switching the tables. If unable to do this, the query will fail.

• Record Management Services; the VAX-based database management system software from Digital Equipment Company (DEC).

• Relational On-line Analytical Processing; on-line analytical processing using summary tables in a relational database. See OLAP. MDD, and MOLAP.

• A file that contains information about the database structure. In OMNIDEX, the OMNIDEX root file contains information about where keys are installed.

• See record.

• A unique representation of a single record in a set of data. See record number.

• A child table indexed with both the primary keys (from parent) and its own row IDs. See Record Specific.

• Configurable options that control certain features of a program, like DBINSTAL, for the duration of a session.