This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
glossary:o [2009/12/04 16:35] tdo |
glossary:o [2012/10/26 14:24] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Glossary: O ====== | + | {{page>:top_add&nofooter&noeditbtn}} |
| + | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| + | ====== Glossary ====== | ||
| + | ===== O ===== | ||
| {{page>:glossary_bar&nofooter&noeditbtn}} | {{page>:glossary_bar&nofooter&noeditbtn}} | ||
| - | ===== Object ===== | + | ==== Object ==== |
| + | * an entity within the Environment that can be accessed and manipulated, a column definition, for example. | ||
| - | * an entity within the Environment that can be accessed and manipulated, a column definition, for example. | + | ==== ODBC ==== |
| + | * Open Database Connectivity; (1) a standard for accessing different databases from PCs or other small workstations, providing a common SQL-based method for translating requests into the database tool's native SQL (2) software developed by Microsoft that enables Windows applications to connect to various databases. | ||
| - | ===== ODBC ===== | + | ==== ODBC Administrator ==== |
| + | * software written by both Microsoft and the ODBC Driver software company to create and maintain DataSources. | ||
| - | * Open Database Connectivity; (1) a standard for accessing different databases from PCs or other small workstations, providing a common SQL-based method for translating requests into the database tool's native SQL (2) software developed by Microsoft that enables Windows applications to connect to various databases. | + | ==== ODBC Driver ==== |
| + | * software written by DISC specifically for Omnidex-enhanced databases; | ||
| + | * the Omnidex module that sends ODBC calls to the Omnidex retrieval engine that accesses the database, attached to a container application by Driver Manager. | ||
| - | ===== ODBC Administrator ===== | + | ==== ODBC-aware applications ==== |
| + | * an application that uses Microsoft's ODBC technology to access databases. | ||
| + | ==== Omnidex ==== | ||
| + | * an advanced indexing product from Dynamic Information Systems Corporation (DISC), providing greater query flexibility than native database methods and accelerating database search and retrieval by reducing I/O. | ||
| - | * software written by both Microsoft and the ODBC Driver software company to create and maintain DataSources. | + | ==== Omnidex Access ==== |
| + | * The Omnidex open systems API that performs the index look-ups, qualifying counts, and data retrievals, including the routines oaqualify, oaselect, and oafetch. Also known as OmniAccess. | ||
| - | ===== ODBC Driver ===== | + | ==== Omnidex Environment ==== |
| + | ==== Omnidex condition word ==== | ||
| + | * word 11 of the status array, which contains an error code if a call to an Omnidex intrinsic failed. | ||
| - | * software written by DISC specifically for Omnidex-enhanced databases; | + | ==== Omnidex detail ==== |
| - | * the Omnidex module that sends ODBC calls to the Omnidex retrieval engine that accesses the database, attached to a container application by Driver Manager. | + | * a detail set linked to an Omnidex master by an Omnidex SI (search item). |
| - | ===== ODBC-aware applications ===== | + | ==== Omnidex domain ==== |
| + | * see Domain. | ||
| - | * an application that uses Microsoft's ODBC technology to access databases. | + | ==== Omnidex error indicator ==== |
| + | * the word of the status array that indicates whether an error has occurred. This word differs between default (active) error handling and passive error handling. | ||
| - | ===== Omnidex ===== | + | ==== Omnidex ID ==== |
| + | * a binary integer (I2, J2, or K2) value that is used to identify records during keyword searches (for Multiple keys); | ||
| + | * the arbitrary sequential ID of a record assigned by Omnidex. | ||
| + | * Also known as ODXID or ODX ID | ||
| - | * an advanced indexing product from Dynamic Information Systems Corporation (DISC), providing greater query flexibility than native database methods and accelerating database search and retrieval by reducing I/O. | + | ==== Omnidex indexes ==== |
| - | ===== Omnidex Access ===== | + | * the indexed columns or composite indexes designated for Omnidex keyword or sorted indexing through the DBINSTAL installation utility program. |
| - | The Omnidex open systems API that performs the index look-ups, qualifying counts, and data retrievals, including the routines oaqualify, oaselect, and oafetch. Also known as OmniAccess. | + | |
| - | ===== Omnidex Environment ===== | + | |
| + | ==== Omnidex Intrinsic Interface ==== | ||
| + | * Omnidex intrinsics that provide retrieval access to Multiple and Sorted key indexes and maintenance to Omnidex indexes. | ||
| + | ==== Omnidex master ==== | ||
| + | * a master data set that contains one or more fields specified for Omnidex keyword retrieval, or a master that is linked by the Omnidex SI to a detail that contains one or more Multiple keys. | ||
| - | ===== Omnidex condition word ===== | + | ==== Omnidex root file ==== |
| + | * the index file that contains information about the database structure, including which fields are specified for Omnidex retrieval. | ||
| + | ==== Omnidex Search Item ==== | ||
| + | * the search item field in an Omnidex master which may also be the Omnidex ID for the set (that is, the SI-ID). See Search Item. | ||
| - | * word 11 of the status array, which contains an error code if a call to an Omnidex intrinsic failed. | + | ==== One-to-many relationship ==== |
| - | ===== Omnidex detail ===== | + | * refers to data entities where one entity corresponds to many other entities, as in the case of a search item value to many detail records. |
| - | ===== | + | ==== One-to-one relationship ==== |
| + | * refers to data entities where one entity corresponds to only one other entity, as in the case of a search item value to a master record. | ||
| + | ==== Operator ==== | ||
| + | * any special character or token used in Omnidex retrievals, for example, the Multifind operator (&). | ||
| - | * a detail set linked to an Omnidex master by an Omnidex SI (search item). | + | ==== OR criteria ==== |
| + | * Multiple criteria values or predicates that records must match one or more of, but not all. | ||
| - | ===== Omnidex domain ===== | + | ==== Outer join ==== |
| + | * A join that includes all rows from joined tables that meet the specified search criteria. Rows without matching records in the joined table are matched with null values. | ||
| - | * see Domain. | + | {{page>:bottom_add&nofooter&noeditbtn}} |
| - | + | ||
| - | ===== Omnidex error indicator ===== | + | |
| - | + | ||
| - | * the word of the status array that indicates whether an error has occurred. This word differs between default (active) error handling and passive error handling. | + | |
| - | + | ||
| - | ===== Omnidex ID ===== | + | |
| - | + | ||
| - | * a binary integer (I2, J2, or K2) value that is used to identify records during keyword searches (for Multiple keys); | + | |
| - | * the arbitrary sequential ID of a record assigned by Omnidex. | + | |
| - | * Also known as ODXID or ODX ID | + | |
| - | + | ||
| - | ===== Omnidex indexes ===== | + | |
| - | + | ||
| - | * the indexed columns or composite indexes designated for Omnidex keyword or sorted indexing through the DBINSTAL installation utility program. | + | |
| - | + | ||
| - | ===== Omnidex Intrinsic Interface ===== | + | |
| - | + | ||
| - | * Omnidex intrinsics that provide retrieval access to Multiple and Sorted key indexes and maintenance to Omnidex indexes. | + | |
| - | + | ||
| - | ===== Omnidex master ===== | + | |
| - | + | ||
| - | * a master data set that contains one or more fields specified for Omnidex keyword retrieval, or a master that is linked by the Omnidex SI to a detail that contains one or more Multiple keys. | + | |
| - | + | ||
| - | ===== Omnidex root file ===== | + | |
| - | + | ||
| - | * the index file that contains information about the database structure, including which fields are specified for Omnidex retrieval. | + | |
| - | + | ||
| - | ===== Omnidex Search Item ===== | + | |
| - | + | ||
| - | * the search item field in an Omnidex master which may also be the Omnidex ID for the set (that is, the SI-ID). See Search Item. | + | |
| - | + | ||
| - | ===== one-to-many relationship ===== | + | |
| - | + | ||
| - | * refers to data entities where one entity corresponds to many other entities, as in the case of a search item value to many detail records. | + | |
| - | + | ||
| - | ===== one-to-one relationship ===== | + | |
| - | + | ||
| - | * refers to data entities where one entity corresponds to only one other entity, as in the case of a search item value to a master record. | + | |
| - | + | ||
| - | ===== operator ===== | + | |
| - | + | ||
| - | * any special character or token used in Omnidex retrievals, for example, the Multifind operator (&). | + | |
| - | + | ||
| - | ===== OR criteria ===== | + | |
| - | + | ||
| - | * Multiple criteria values or predicates that records must match one or more of, but not all. | + | |
| - | + | ||
| - | ===== outer join ===== | + | |
| - | + | ||
| - | * A join that includes all rows from joined tables that meet the specified search criteria. Rows without matching records in the joined table are matched with null values. | + | |