Show page
Old revisions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
dev:tutorials:simple_envrionment_flat [2010/05/21 14:00]
tdo 		dev:tutorials:simple_envrionment_flat [2016/06/28 22:38] (current)
Line 23: Line 23:
 </​code>​ </​code>​
  
-This creates an Omnidex Environment named "​tinyenv"​ with a single Database named "​tinydb"​ with one table named "​table1"​. ​ Because the DATABASE TYPE is "​flatfile",​ the name of the underlying operating system file for this table is "​table1"​. ​ Typically a filespec location would be used.  Copy and save this environment as "tiny.src".+This creates an Omnidex Environment named "​tinyenv"​ with a single Database named "​tinydb"​ with one table named "​table1"​. ​ Because the DATABASE TYPE is "​flatfile",​ the name of the underlying operating system file for this table is "​table1"​. ​ Typically a filespec location would be used.  Copy and save this environment as "tiny.sql". 
 ==== Step 2 - Creating the Omnidex Environment Catalog ==== ==== Step 2 - Creating the Omnidex Environment Catalog ====
  
Line 31: Line 32:
   odxsql> exit   odxsql> exit
 </​code>​ </​code>​
- 
 ==== Step 3 - Use OdxSQL to test, verify and manipulate the Environment ==== ==== Step 3 - Use OdxSQL to test, verify and manipulate the Environment ====
  
-  os> odxsql tiny.env+  os> odxsql tiny.xml
  
 or or
  
   os> odxsql   os> odxsql
-  > connect tiny.env +  > connect tiny.xml
- +
-  > create file table1 +
- +
-  > insert into table1 values (1) +
- +
-  > select * from table1 +
 <​code>​ <​code>​
- 
-C:​\dev\odx\tiny>​more tiny.src 
-ENVIRONMENT tinyenv 
-DATABASE tinydb 
-  TYPE flatfile 
-TABLE table1 
-  COLUMN mysq DATATYPE INTEGER 
-  COLUMN mytext DATATYPE CHAR(60) 
- 
-C:​\dev\odx\tiny>​oacomp tiny.src tiny.env 
-OACOMP - Omnidex Environment Compiler ​                 Mon Nov 30 21:41:50 2009 
-(c) Dynamic Information Systems Corp.  1981-2009 ​                  5.0 Build 1H 
-Microsoft Windows XP Professional SP 3 (2600) ​                       TDO830/TDO 
-** Trial Copy ** 
- 
-Parsed; Validated; Compiled; Done 
-** Environment Compiled Successfully! ** 
  
  
-C:​\dev\odx\tiny>​odxsql tiny.env+C:​\dev\odx\tiny>​odxsql tiny.xml
 ODXSQL - Omnidex SQL                                   Mon Nov 30 21:41:59 2009 ODXSQL - Omnidex SQL                                   Mon Nov 30 21:41:59 2009
 (c) Dynamic Information Systems Corp.  1981-2009 ​                  5.0 Build 1H (c) Dynamic Information Systems Corp.  1981-2009 ​                  5.0 Build 1H
Line 74: Line 50:
  
  
-Connected to C:​\dev\odx\tiny\tiny.env+Connected to C:​\dev\odx\tiny\tiny.xml
 > create file table1 > create file table1
 File table1 created File table1 created
Line 94: Line 70:
  
  
-1 row returned+3 rows returned
 > >
 </​code>​ </​code>​
Line 100: Line 76:
  
 <​code>​ <​code>​
-C:​\dev\odx\tiny>​dbinstal +C:​\dev\odx\tiny>​odxsql ​tiny.xml 
-DBINSTAL - Omnidex Database Indexing Utility ​          Tue Dec 01 07:30:37 2009 +update ​indexes
-(c) Dynamic Information Systems Corp.  1981-2009 ​                  5.0 Build 1H +
-Microsoft Windows XP Professional SP 3 (2600) ​                       TDO830/​TDO +
-** Trial Copy ** +
- +
-Database or Environment: ​tiny.env +
- +
-Cmd: install +
- +
-** OMNIDEX MultiDimensional/​Keyword (MDK) Index Installation ** +
- +
-Enter Tables and Columns to be indexed +
- +
-To create an index comprised of all or parts of one or more columns, +
-enter an Index Name followed by '​!'​ at the Column prompt +
- +
-Enter '?'​ for a list of Tables or Columns, '/'​ to exit the current prompt +
- +
-Table name? table1 +
- +
-To index this table in any parent domains, enter the +
-column linking it to its parent or '​P='​ followed by the parent name +
- +
-Link column 1: / +
-Table will be indexed in its own domain +
-Column name: mytext;kw +
-Column name: / +
-Table name? / +
- +
-Specification of MDK indexes ​is complete +
- +
-** OMNIDEX Aggregation/​Sorted_Key (ASK) Index Installation ** +
- +
-Table name? / +
- +
-Proceed with installation?​ [Y] +
- +
-Use the Build command to load the following indexes: +
- +
-TABLE1 (Omnidex MDK) +
- +
-Cmd: build +
-Table [;key] table1 +
-Unloading keywords +
-TABLE1: 3 records (15 keywords) processed +
-15 keywords unloaded +
-0 (0MB), 1 (1MB), 0 (0MB) +
-Loading keywords +
- +
-15 keywords loaded +
-2 blocks used, 2 levels +
-Indexing complete. ​ CPU time: 0:​00:​00 ​ Elapsed: 0:00:00 +
- +
-Cmd: quit +
- +
-C:​\dev\odx\tiny>​+
 </​code>​ </​code>​
 ==== Step 5 - Develop an Application with ODBC, JDBC or Stored Procedures ==== ==== Step 5 - Develop an Application with ODBC, JDBC or Stored Procedures ====
  
-After creating an Omnidex Environment and adding Omnidex indexes via DBINSTAL, applications can be developed using the DISC provided ODBC and JDBC drivers.+After creating an Omnidex Environment and adding Omnidex indexes via UPDATE INDEXES, applications can be developed using the DISC provided ODBC and JDBC drivers.
  
-Create ​an ODBC or JDBC datasource ​using the Windows Client DataSource Editor (DSEDIT). +Network aware Omnidex applications can either use an ODBC style datasource file or an internal connection string.
- +
-Name the file as "​tiny.dsn"​. +
- +
-Or modify the following text file and save as tiny.dsn. +
-Change the following lines to the correct path and filenames. +
- +
-Change these three lines with: +
-  * Host= Change this value to the name of computer being used for this test. +
-  * ODBCDSNFILE= Change this value to the path and file name of the dsn file. +
-  * FileSpec= Change this value to the path and filename of the Omnidex Environment file. +
- +
-Cut and paste this text as "​tiny.dsn"​ with the modifications and save in the same directory as the "​tiny.env"​ Omnidex Environment file. +
- +
-<​code>​ +
-Host=tdo830 +
-ODBCDSNFILE=C:​\dev\odx\tiny\tiny.dsn +
-FileSpec=c:​\dev\odx\tiny\tiny.env +
-</​code>​ +
- +
-<​code>​ +
-ODBC] +
-DRIVER=DISC OMNIDEX OdxNet Driver +
-ODBCDSNFILE=C:​\dev\odx\tiny\tiny.dsn +
-ODBCDSNNAME=tinydsn +
-[DataSources] +
-tinydsn=DataSource Edit Wizard Generated +
-[DataSource tinydsn] +
-Dictionary=tinydsn +
-DisplayWindow=NONE +
-[Dictionaries] +
-tinydsn=DataSource Edit Wizard Generated +
-[Dictionary tinydsn] +
-Server=Server1 +
-NetworkServices=OdxNet +
-Type=OmniAccess +
-FileSpec=c:​\dev\odx\tiny\tiny.env +
-HostOAConnectOptions= +
-Password=!~ +
-AccessOptions=Write +
-[Servers] +
-Server1=DataSource Edit Wizard Generated +
-[Server Server1] +
-Host=tdo830 +
-Port=7555 +
-</​code>​+
 ==== Step 6 - Simulate a client server environment using OdxNet with ODBC or JDBC ==== ==== Step 6 - Simulate a client server environment using OdxNet with ODBC or JDBC ====
  
Line 216: Line 92:
 Go back to the original command window and do the following: Go back to the original command window and do the following:
  
-   ​os>​ odxsql tiny.dsn -odbc+   ​os>​ odxsql tiny -odbc
  
 or run an ODXNET listener from within OdexSQL using the -odxnet command line option. or run an ODXNET listener from within OdexSQL using the -odxnet command line option.
  
    ​os>​ odxsql -odxnet    ​os>​ odxsql -odxnet
-   > connect tiny.dsn using odbc+   odxsql> connect tiny using odbc
               ​               ​
 <​code>​ <​code>​
-   > select * from table1 where mytext = '​bears'​+   odxsql> select * from table1 where mytext = '​bears'​
  
 MYSEQ        MYTEXT MYSEQ        MYTEXT
Line 232: Line 108:
 </​code>​ </​code>​
  
-### Note that Omnidex will do a quick text (Keyword) retreival automatically ##+### Note that Omnidex will do a quick text (Keyword) retreival automatically ​###
  
 ==== Step 7 - Insert a new row to see that it is indexed ==== ==== Step 7 - Insert a new row to see that it is indexed ====
 
Back to top
dev/tutorials/simple_envrionment_flat.1274450437.txt.gz · Last modified: 2016/06/28 22:38 (external edit)
Sitemap Recent Changes