DISC

Contents | What's New | Quick Links

 

Omnidex Environments

Introduction

Software Installation

Concepts and Design

Designing Applications

Omnidex Environments

SQL Reference

Omnidex API's

Utilities

Interfaces

Performance Guide

Troubleshooting Guide

Appendix

 

 

Omnidex Environments

 

An environment is a collection of objects representing a database schema. An object is an entity within the environment corresponding to a piece of that schema, like a table or column, that can be accessed and manipulated, either directly or through an application. Data management systems like Oracle are sophisticated environments, organizing data into tables based on a system dictionary.

Syntax

Database Specifics

The Omnidex Environment Catalog is a superset of schemas, characterizing one or more environments in a single file. At the same time, it is a subset of the information within those schemas, describing only the information pertinent to the application. It organizes data into a system of defined objects that you can access and manipulate through Omnidex applications, and defines the relationships between those objects and any native indexing structures available for data retrieval.

An Environment Catalog is divided into several sections, each of which defines a different aspect of the environment. Within each of these sections are statements that define some object, like a DATABASE, TABLE or COLUMN in the Environment. These statements declare a name for the object, as well as certain attributes, like the DATATYPE and LENGTH of a column.

In a flat-file environment, the fundamental objects are files and rows, and their organization is solely a function of the application programs that access them.

The following is a simple example Environment source file:

Environment start_env

Database start

Type flatfile

table sales_facts

column odx_seq_ID datatype INTEGER length 2

column acct datatype CHAR length 10

column amount datatype INTEGER length 4

The Environment Catalog source files are created using any system text editor. Alternatively, for Oracle, Sybase, Informix, and TurboImage, the Environment Catalogs can be automatically generated through the Omnidex utility OAHELPER.

The Omnidex utility OACOMP is used to compile the Environment source file into the Environment object file, also called the compiled Environment Catalog file. If the original Environment source file is needed but unavailable, the Omnidex utility OADECOMP will create a separate Environment source file from an existing compiled Environment file.

 

top

Dynamic Information Systems Corporation - Omnidex Version 3.8 Build 6 J15.03-Copyright © 2003

DISC | Documentation Home