This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
programs:odxsql:commands:connect [2009/11/28 20:50] tdo |
programs:odxsql:commands:connect [2016/06/28 22:38] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
{{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
<html><div align="center"><span style="color:red">DRAFT</span></div></html> | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
+ | ====== OdxSQL Connect Environment ====== | ||
+ | ===== Description ===== | ||
+ | CONNECT establishes a connection to an Omnidex Environment and opens a cursor. | ||
- | Example | + | CONNECT is followed by either an Omnidex Environment filespec or a File DSN for ODBC, JDBC or CLOA connections. |
- | In OdxSQL, CONNECT establishes a connection to an Omnidex Environment Catalog and opens a cursor. | + | |
- | Enter CONNECT followed by the environment catalog file spec and any desired parameters at the prompt. | + | ===== Syntax ===== |
- | >connect orders.env | + | CONNECT [TO] Omnidex_Environment |
- | Connected to C:\Omnidex\Demodata\orders.env | + | [ON host[:port]] |
- | > | + | [AS [user]/[password]] |
+ | [USING api] | ||
+ | [WITH options] | ||
+ | ===== Discussion ===== | ||
- | Or, type CONNECT and press return to be prompted for each parameter. | + | == Omnidex Environment == |
+ | Reuired: This is the Omnidex Environment or ODBC or JDBC File DSN. If connecting to a File DSN then the USING api clause with ODBC, JDBC or OA needs to be specified. | ||
+ | |||
+ | == [ON host[:port]] == | ||
+ | Optionally specifiy the Host and Port for a network connection. | ||
+ | |||
+ | == [AS [user]/[password]] == | ||
+ | |||
+ | Optionally specify a username and password in the AS [ user]/[ password] clause. | ||
+ | |||
+ | == [USING api] == | ||
+ | Optionally specify which API to use for processing subsequent statements. The USING clause facilitates the testing of ODBC and JDBC environments for testing and optimization. | ||
+ | |||
+ | Allowable values for API are: | ||
+ | * ODBC - Open Data Base Connectivity | ||
+ | * JDBC - Java Data Base Connectivity | ||
+ | * CLOA - Client OmniAccess. | ||
+ | * OA - OmniAccess - this is the default if no USING clause is specified. | ||
+ | |||
+ | == [WITH options] == | ||
+ | |||
+ | Optionally specify connect options in the WITH clause. | ||
+ | |||
+ | The NOCURSOR option will cause a connection to be established without opening a cursor. | ||
+ | |||
+ | ===== Examples ===== | ||
+ | |||
+ | >connect orders.env | ||
+ | Connected to C:\Omnidex\Demodata\orders.env | ||
+ | | ||
- | >connect | ||
- | Environment file: /disctest/oracle/orders.env | ||
- | User: guest | ||
- | Password: | ||
- | Options: | ||
- | Enter / to exit the series of prompts at any time. | ||
- | Specify a username and password in the AS [ user]/[ password] clause. | ||
- | Specify connect options in the WITH clause. | ||
- | The NOCURSOR option, will cause a connection to be established without opening a cursor. | ||