This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
glossary:e [2009/12/04 05:47] tdo |
glossary:e [2012/10/26 14:46] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Glossary: E ====== | + | {{page>:top_add&nofooter&noeditbtn}} |
| + | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| + | ====== Glossary ====== | ||
| + | ===== E ===== | ||
| {{page>:glossary_bar&nofooter&noeditbtn}} | {{page>:glossary_bar&nofooter&noeditbtn}} | ||
| - | ===== Environment ===== | + | ==== Environment ==== |
| + | An Environment, also know as an Omnidex Environment is the combination of: | ||
| + | * An Omnidex Environment File containing metadata | ||
| + | * Connection to one or more databases or raw data files | ||
| + | * One or more sets of Omnidex index files. | ||
| - | a set of objects that can be manipulated to determine a user's access to data. An Environment determines what data is available to a user, what access a user has to that data, and so on. | + | ==== Environment Catalog ==== |
| + | * A file that contains compiled environment information about how Omnidex source data is organized, what users can access it, and how they can access it. | ||
| + | * Environment Catalogs are created using the OACOMP utility from and Environment Source file. | ||
| + | * Environment Catalogs are using stored in files with a .env file suffix. | ||
| + | * Environment Catalogs are still supported but as of version 5.1, CREATE statements from OdxSQL is the typical approach to creating and maintaining Omnidex metadata information which is stored in the Omnidex Environment File. | ||
| - | ===== Environment Catalog ===== | + | ==== Environment File ==== |
| + | * A physical operating system file that contains Omnidex metadata information. | ||
| + | * Environment Files are created using the CREATE ENVIRONMENT DDL statement. | ||
| + | * Environment Files use an xml layoug and are typically stored with an .xml file suffix. | ||
| + | * As of Omnidex Version 5.1, Environment Files are preferred over compiled Environment Catalogs. | ||
| - | a file that contains information about how data is organized, what users can access it, and how they can access it. | + | ==== Excluded words list ==== |
| + | * An ASCII file containing words to exclude from indexing. Also called an excluded words file. | ||
| - | ===== Excluded words list ===== | + | ==== Excluded words ==== |
| + | * Words specified through OmniUtil for exclusion from the Omnidex indexes. | ||
| - | an ASCII file containing words to exclude from indexing. Also called an excluded words file. | + | ==== Executable library ==== |
| - | + | * XL; the location of the Omnidex intrinsics and call conversion procedures in native mode versions of Omnidex; | |
| - | **excluded words** | + | |
| - | words specified through OmniUtil for exclusion from the Omnidex indexes. | + | |
| - | + | ||
| - | **executable library** | + | |
| - | XL; the location of the Omnidex intrinsics and call conversion procedures in native mode versions of Omnidex; | + | |
| the HPPA native mode library of callable routines. | the HPPA native mode library of callable routines. | ||
| - | **extract** | + | ==== extract ==== |
| - | specific data selected and retrieved from an existing database, usually from an OLTP system for use in data warehousing. See OLTP and data warehouse. | + | * Specific data selected and retrieved from an existing database, usually from an OLTP system for use in data warehousing. See OLTP and data warehouse. |
| SQL function that "extracts" specific parts of a date. | SQL function that "extracts" specific parts of a date. | ||
| ODXSQL function that creates SQL insert, update, and delete statements for a table to allow a user to restore a table to its original state. | ODXSQL function that creates SQL insert, update, and delete statements for a table to allow a user to restore a table to its original state. | ||
| + | ==== Explain Plan ==== | ||
| + | * Detailed description of the Omnidex SQL data access plan to facilitate optimization operations to improve retrieval speed. | ||
| + | ==== Expression Based Columns ==== | ||
| + | * Columns that are derived from a SQL Expression that can be indexed by Omnidex. The column does not physically exist in the table but is still available for indexing. | ||
| - | **extranet** | + | These columns are specified in the CREATE TABLE statement. |
| - | an Internet-based network where data is shared between one company and another, typically business partners. | + | |
| - | + | ||
| - | Explain Plan | + | |
| + | CREATE TABLE mytable | ||
| + | ... | ||
| + | (col1 | ||
| + | city_initial character(1) as "substring(city from 1 for 1)" omnidex, | ||
| + | ... | ||
| - | ====== Quick Links ====== | + | {{page>:bottom_add&nofooter&noeditbtn}} |
| - | {{page>:quicklinks&nofooter&noeditbtn}} | + | |