Differences

This shows you the differences between two versions of the page.

--- glossary:c [2009/07/23 02:18]
admin
+++ glossary:c [2012/10/26 14:46] (current)
@@ Line 1: / Line 1: @@
-====== Glossary: C ======
+{{page>:top_add&nofooter&noeditbtn}}
+====== Glossary ======
 ===== C =====
-**calling errors**
+{{page>:glossary_bar&nofooter&noeditbtn}}
-Syntax errors that cause programs to fail.
+==== C String Omnidex Datatype ====
+  * A legacy Omnidex datatype name that is now referred to "String".  A datatype in Omnidex that refers to a string terminated with a null just like strings in the C language.  C Strings are used as a return data type from many Omnidex SQL Functions.  C Strings are recommended over the Varchar datatype because of internal performance.
-**cardinality**
-A term indicating the number of:
-unique values in a column
-rows in a table
-With respect to databases, there are two distinct types of cardinality: table cardinality and column cardinality.
-Table cardinality is the number of rows in a table.
+==== Cardinality ====
-Column cardinality is the number of unique values in a column.
+  * A term indicating the number of unique values in a column or the number of rows in a table.
-Omnidex uses these values to determine the best method to use to process a query against multiple tables.
-For example:
+  * With respect to databases, there are two distinct types of cardinality: table cardinality and column cardinality.
+  * Table cardinality is the number of rows in a table.
+  * Column cardinality is the number of unique values in a column.
+  * Omnidex uses these values to determine the best method to use to process a query against multiple tables.
+== For example: ==
 The products table is a parent table with a primary key that has a column cardinality of 10,000. This means it has 10,000 unique product codes.
 The orders table is a child table with 10,000,000 rows. This means it has a table cardinality of 10,000,000.
-SELECT O.PRODUCT_CODE, O.CUSTOMER_NO, O.STATUS
+<code SQL>
-FROM PRODUCTS P, ORDERS O
+  SELECT O.PRODUCT_CODE, O.CUSTOMER_NO, O.STATUS
-WHERE P.PRODUCT_CODE=O.PRODUCT_CODE
+      FROM PRODUCTS P, ORDERS O
-AND P.PRODUCT_NAME = 'PRINTER'
+      WHERE P.PRODUCT_CODE=O.PRODUCT_CODE
+      AND P.PRODUCT_NAME = 'PRINTER'
+</code>
+==== Cartesian product ====
+  * A dataset consisting of every possible combination of rows from mulitple tables.
-**cartesian product**
-A dataset consisting of every possible combination of rows from mulitple 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**
+==== 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
+  * A list containing data elements where each data element has a pointer to the previous and successive data element. See also: linked list
-**child**
+==== Child ====
-A child table or detail data set.
+  * A child table or detail data set.
-**child key**
+==== 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
+  * 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**
+==== Child table ====
-A table subordinate to a parent table or master data set.
+  * 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.
+  * 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.
+  * 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**
+==== 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.
+  * 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**
+==== 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.
+  * 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**
+==== 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.
+  * 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**
+==== 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.
+  * 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.
-**criteria count**
+==== Column cardinality ====
-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.
+  * The number of unique values in a column. See also: cardinality, table cardinality
-**cursor**
+==== Composite index ====
-A working area that defines the current position of a process in an open environment.
+  * 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
-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.
+==== 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.
+==== 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.
+==== Contains ====
+  * See Also [[dev:sql:functions:contains:home | $CONTAINS ]]
+==== Custom Indexes ====
-Contains
+{{page>:bottom_add&nofooter&noeditbtn}}
-Custom Indexes
-====== Quick Links ======
-{{page>:quicklinks&nofooter&noeditbtn}}

Back to top

glossary/c.1248315521.txt.gz · Last modified: 2012/10/26 14:40 (external edit)

Sitemap Recent Changes