This is an old revision of the document!


DRAFT

Omnidex SQL: CONNECT

Description

CONNECT establishes a connection to an Omnidex Environment. Before any Omnidex operations can be performed on an Omindex enhanced data store, a connection must be established.

Note that when using the Omnidex ODBC and Omnidex JDBC driver, connections are established using ODBC and JDBC calls.

The Omnidex CONNECT Statement is primarily used within OdxSQL.

Syntax

CONNECT [TO] [ [host:port] ]environment_filespec[ [node_name] ]
        [ON host[:port]] 
        [AS [user]/[password]]
        [USING < ODBC | JDBC | CLOA > ] 
        [WITH options]

Discussion

[TO] [ [host:port] ]Environment_filespec

Specifies the Omnidex XML Environment containing the Omnidex metadata.

connect odx.xml;

[AS [user]/[password]]

Used to specify a username and password if required by the underlying relational database.

[WITH options]

Options specific to the CONNECT command.

MAINTENANCE

Connect to an Omnidex Environment in maintenance mode to facilitate Omnidex index maintenance.

Options

read
write
exclusive
ia
da
oa
envaccess
eapreload
eacache
iacache
dacache
iafiles
dbdirect
dbinstal
dbuser
dbaccess
maxfopens
maxmemory
cache
singledbconnect
userlocking
preprocessor
interrupts
clocks
autopseudocolumns
setcwd
      EACACHE=<DEFAULT | ON | OFF | MIN | MAX | n>
DACACHE=<DEFAULT | ON | OFF | MIN | MAX | n>
IACACHE=<DEFAULT | ON | OFF | MIN | MAX | n>
DEFAULT	Set threshold to the default value as shown above
ON		Same as DEFAULT
OFF		Set threshold to 0, forcing resources to be freed as soon as they are released.
MIN		Same as OFF
MAX		Set threshold to 2.1 Gig (a theoretically unreachable number)
n		Set threshold to the specified number, measured in kilobytes (1024 bytes).

Examples

 
Back to top
dev/sql/statements/connect/home.1278047162.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)