Omnidex Development Quick Reference

Omnidex Environments are used to specify information on the location and layout of the underlying data and how the data is indexed with the Omnidex indexes.

/* Simple Star Schema */
create environment    
 in                   "simple.xml"
 with                 delete;


create database       "SIMPLE"
  type                FLATFILE
  index_directory     "idx\SIMPLE_"
 in                   "simple.xml";


create table          "COUNTRIES"
 physical             "dat\cnt.dat"
 (
  "COUNTRY"           CHARACTER(2)      omnidex,
  "DESCRIPTION"       C STRING(47)      quicktext,
  "LATITUDE"          FLOAT             omnidex      usage "LATITUDE",
  "LONGITUDE"         FLOAT             omnidex      usage "LONGITUDE",
  "CAPITAL"           C STRING(31)      quicktext,
  "CAPITAL_LAT"       FLOAT             omnidex      usage "LATITUDE",
  "CAPITAL_LONG"      FLOAT             omnidex      usage "LONGITUDE",
  constraint COUNTRIES_COUNTRY_PK primary ("COUNTRY")
 )
 in                   "simple.xml";


create table          "STATES"
 physical             "dat\sta.dat"
 (
  "STATE"             CHARACTER(2)      omnidex,
  "DESCRIPTION"       C STRING(31)      quicktext,
  "STATE_CODE"        CHARACTER(2)      omnidex,
  "REGION"            CHARACTER(2)      omnidex,
  "COUNTRY"           CHARACTER(2)      omnidex,
  "TAX_RATE"          FLOAT             omnidex,
  constraint STATES_STATE_PK primary ("STATE"),
  constraint STATES_COUNTRY_FK foreign ("COUNTRY") references "COUNTRIES"
 )
 in                   "simple.xml";


create table          "GENDERS"
 physical             "dat\gdr.dat"
 (
  "GENDER"            CHARACTER(1)      omnidex,
  "DESCRIPTION"       C STRING(31)      quicktext,
  constraint GENDERS_GENDER_PK primary ("GENDER")
 )
 in                   "simple.xml";


create table          "HOUSEHOLDS"
 physical             "dat\households.dat"
 (
  "HOUSEHOLD"         CHARACTER(12)     omnidex,
  "ADDRESS"           CHARACTER(50)     quicktext,
  "CITY"              CHARACTER(28)     quicktext,
  "STATE"             CHARACTER(2)      omnidex,
  "ZIP"               CHARACTER(5)      omnidex,
  "COUNTRY"           CHARACTER(2)      omnidex,
  constraint HOUSEHOLDS_HOUSEHOLD_PK primary ("HOUSEHOLD"),
  constraint HOUSEHOLDS_STATE_FK foreign ("STATE") references "STATES",
  constraint HOUSEHOLDS_COUNTRY_FK foreign ("COUNTRY") references "COUNTRIES"
 )
 in                   "simple.xml";


create table          "INDIVIDUALS"
 physical             "dat\individuals.dat"
 (
  "INDIVIDUAL"        CHARACTER(12)     omnidex,
  "HOUSEHOLD"         CHARACTER(12)     omnidex,
  "NAME"              CHARACTER(50)     quicktext,
  "GENDER"            CHARACTER(1)      omnidex bitmap,
  "BIRTHDATE"         ANSI DATE         omnidex,
  "PHONE"             CHARACTER(14)     omnidex,
  "EMAIL"             CHARACTER(60)     quicktext,
  constraint INDIVIDUALS_INDIVIDUAL_PK primary ("INDIVIDUAL"),
  constraint INDIVIDUALS_HOUSEHOLD_FK foreign ("HOUSEHOLD") references "HOUSEHOLDS",
  constraint INDIVIDUALS_GENDER_FK foreign ("GENDER") references "GENDERS",
 )
 in                   "simple.xml";

• ODBC
• JDBC
• RDBMS Stored Procedure Interface

• Debugging

• Environment Catalog Syntax

• Simple Environment on Flat File

Omnidex Development uses the following main components of the Omnidex Software.

• Omnidex Administrator
• OdxSQL
• OdxNet
• OdxAim
• Omnidex ODBC Driver
• Omnidex JDBC Driver
• RDBMS Stored Procedure Interface

• Install Omnidex on Snapshot data store.
• Set up OdxNet Network Services.
• Use OdxSQL to test set up, prototype and optimize queries.
• Write Java Application.

• Install Omnidex on Snapshot data store.
• Set up OdxNet Network Services.
• Use OdxSQL to test set up, prototype and optimize queries.
• Write Java Application.

• Install Omnidex on RDBMS.
• Use OdxSQL to test set up, prototype and optimize queries.
• Write Stored Procedures using the RDBMS Stored Procedure Interface.
• Run OdxAIM to generate Automatic Update Triggers.
• Install Triggers.
• Run OdxAim to monitor and process the triggered updates.

Omnidex Development primarily takes the form of developing either an ODBC or JDBC based application or using either SQL Server or Oracle Stored Procedures.

Applications have also been previously developed using the OmniAccess API (OA) and Client OmniAccess (CLOA) api. DISC recommends that all future Omnidex development use ODBC, JDBC or the Stored Procedure Interface.

• ODBC
• JDBC
• RDBMS Stored Procedure Interface

Applications using Omnidex have been developed using: