This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:sql:statements:connect:home [2010/07/28 21:24] tdo |
dev:sql:statements:connect:home [2016/06/28 22:38] (current) |
||
---|---|---|---|
Line 19: | Line 19: | ||
==== TO ==== | ==== TO ==== | ||
TO is optional and is only included for readability. | TO is optional and is only included for readability. | ||
+ | ==== connection_string ==== | ||
+ | //Connection_string// is a bracketed server name and optional port that directs the connection through the Omnidex Network services. | ||
+ | |||
+ | When using a //connection_string// the USING <ODBC | JDBC > clause must be specified. | ||
+ | |||
+ | connect [server1:7555]odx.xml using ODBC; | ||
+ | |||
+ | Under Windows, the //environment_filespec// must have the backslash directory separater escaped. | ||
+ | |||
+ | connect [server1:7555]c:\\dev\\odx\\myenv.xml using odbc | ||
+ | |||
==== Environment_filespec ==== | ==== Environment_filespec ==== | ||
- | The Environment_filespec specifies the Omnidex XML Environment containing the Omnidex metadata. The keyword TO is optional. | + | The //Environment_filespec// specifies the Omnidex XML Environment containing the Omnidex metadata. The keyword TO is optional. |
connect odx.xml; | connect odx.xml; | ||
Line 41: | Line 52: | ||
==== USING api ==== | ==== USING api ==== | ||
- | Used to specify the either the ODBC or JDBC api to use for access. This is primarily used to test ODBC and JDBC access using OdxSQL. This clause must be specified if using a connection string. | + | Used to specify either the ODBC or JDBC api to use for access. This is primarily used to test ODBC and JDBC access using OdxSQL. This clause must be specified if using a connection string. |
connect [server1:7555]odx.xml using ODBC; | connect [server1:7555]odx.xml using ODBC; |