This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
glossary:c [2009/12/04 17:48] tdo |
glossary:c [2012/10/26 14:46] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{page>:top_add&nofooter&noeditbtn}} | ||
| + | |||
| ====== Glossary ====== | ====== Glossary ====== | ||
| ===== C ===== | ===== C ===== | ||
| {{page>:glossary_bar&nofooter&noeditbtn}} | {{page>:glossary_bar&nofooter&noeditbtn}} | ||
| + | ==== 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. | ||
| + | |||
| + | |||
| - | ==== Calling errors ==== | ||
| - | * Syntax errors that cause programs to fail. | ||
| ==== Cardinality ==== | ==== Cardinality ==== | ||
| * A term indicating the number of unique values in a column or the number of rows in a table. | * A term indicating the number of unique values in a column or the number of rows in a table. | ||
| Line 33: | Line 37: | ||
| ==== 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 ==== | ||
| Line 63: | Line 66: | ||
| ==== Column cardinality ==== | ==== Column cardinality ==== | ||
| * The number of unique values in a column. See also: cardinality, table cardinality | * The number of unique values in a column. See also: cardinality, table cardinality | ||
| - | + | ==== Composite index ==== | |
| - | === **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 | * 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 | ||
| + | ==== Composite keys ==== | ||
| * A logical MDK or ASK field comprised of several fields or parts of fields. See also: composite index | * A logical MDK or ASK field comprised of several fields or parts of fields. See also: composite index | ||
| ==== Connection ==== | ==== Connection ==== | ||
| * A direct link between the application and an environment catalog. | * A direct link between the application and an environment catalog. | ||
| - | |||
| ==== Container application ==== | ==== Container application ==== | ||
| * A computer program, typically ODBC-compliant, that processes data extracted from a database. | * 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. | * Generic applications such as Microsoft Excel, Seagate's Crystal Reports and Brio's BrioQuery, that make generic calls through ODBC to a database. | ||
| Line 81: | Line 83: | ||
| ==== Criteria count ==== | ==== 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. | * 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 ==== | ==== Cursor ==== | ||
| * A working area that defines the current position of a process in an open environment. | * 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. | ||
| + | * 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 ==== | ==== Contains ==== | ||
| * See Also [[dev:sql:functions:contains:home | $CONTAINS ]] | * See Also [[dev:sql:functions:contains:home | $CONTAINS ]] | ||
| Line 92: | Line 96: | ||
| ==== Custom Indexes ==== | ==== Custom Indexes ==== | ||
| + | {{page>:bottom_add&nofooter&noeditbtn}} | ||