This is an old revision of the document!
Omnidex Environment Catalogs are used to specify information to the underlying data how the data is indexed.
create environment "SIMPLE_ENV" 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";
Omnidex Development uses the following main components of the Omnidex Software.
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.
Applications using Omnidex have been developed using:
Language | Example |
---|---|
Java | Java JDBC Simple Connection and Select |
PHP | PHP Simple Connection and Select |
C++ | Windows C++ Simple Connection and Select |
C# | Windows C# Simple Connection and Select |
TransactSQL | SQL Server TransactSQL Stored Procedure Example |
PL/SQL | Oracle PL/SQL Stored Procedure Example |
C | |
Visual Basic | |
Cold Fusion | |
Microsoft Access | |
Microsoft Excel | |
MicroStrategy | |
Oracle Business Intelligence | |
SAP Business Objects | |
Activant Speedware 4th GL |