Glossary - C

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

calling errors

• Syntax errors that cause programs to fail.

cardinality

• A term indicating the number of:
• unique values in a column
• rows in a table

cartesian product

• A dataset consisting of every possible combination of rows from multiple tables.
  For example: Customers is the parent table and activity and orders are the child tables. Selecting from both the activity and orders table for a particular customer will produce a cartesian product. Meaning, every row in the activity table will be qualified with every row in the orders table. If activity has 10 rows for one customer and orders has 10 rows for the same customer, the cartesian product is 100 rows.
• table1 (t1) contains 2 rows (r1, r2) and table2 (t2) contains 3 rows (r1, r2, r3). The cartesian product or these tables contains 6 rows: t1r1-t2r1, t1r1-t2r1, t1r1-t2r3, t1r2-t2r1, t1r2-t2r2, t1r2-t2r3.

chained list

• A list containing data elements where each data element has a pointer to the previous and successive data element. See also: linked list

child

• A child table or detail data set.

child key

• A column or field in a child table that identifies rows in the table containing the same values; also known as a repeating key. See also: key

child table

• A table subordinate to a parent table or master data set.
• A table where several rows may share the same identifying value for any given column.
• Child rows are not usually uniquely identifiable by the contents of a single field.
  There is a one-to-many relationship between the parent table and the child table.

client

• The user interface aspect of a client/server system, usually a personal computer or small computer workstation dedicated to immediate, local user interactions, such as system navigation and help, rather than widely accessed or centralized computational activity, such as data processing.

client/server

• A distributed technology approach, or system, where computer processing is divided by function to take advantage of processing on multiple computer units, dividing tasks between client activities and server activities. See client and server.

codified data

• Data represented by codes instead of actual data values, used by data warehouses to conserve data storage space, e.g., income ranges represented by a single character.

column

• A logical representation of a field in individual rows for a given table or view. A column defines a set of fields that share the same data and the same position (offset and length) for any given row in a table.

column cardinality

• The number of unique values in a column. See also: cardinality, table cardinality

composite index

• A type of Omnidex index that lets you index data from either a part or a combination of parts of columns, or entire columns (one or more items from a field). You can create composite indexes in DBINSTAL during Omnidex installation. See also: composite keys

composite keys

• A logical MDK or ASK field comprised of several fields or parts of fields. See also: composite index

connection

• A direct link between the application and an environment catalog.

container application

• A computer program, typically ODBC-compliant, that processes data extracted from a database.
• Generic applications such as Microsoft Excel, Seagate's Crystal Reports and Brio's BrioQuery, that make generic calls through ODBC to a database.
• Applications that work with a database through an ODBC driver.

CPU

• Central Processing Unit. A single computer or functional computing machine that executes program instructions.

criteria count

• A count of the number of rows qualified for the current set of criteria. This count differs from the qualifying count which returns the total number of rows qualified when the rows found in the current search are merged with the rows in the qualified subset. This applies to oaqualify and the SQL extended command, QUALIFY.

cursor

• A working area that defines the current position of a process in an open environment.
• In OmniAccess, cursors are established by a call to oaopencursor, and closed by a call to oaclosecursor. They are referenced through the cursor option as an integer value in calls to OmniAccess routines.
• In ODBC and JDBC, cursors are created with statement objects.

Top