This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
dev:sql:statements:connect:home [2010/07/28 21:24] tdo |
dev:sql:statements:connect:home [2010/07/29 20:40] tdo |
||
|---|---|---|---|
| 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 33: | Line 44: | ||
| connect odx.xml[node1]; | connect odx.xml[node1]; | ||
| - | ==== ON host:port ==== | ||
| - | Specifies that the Environment Catalog is located on a remote server and the Omnidex Network Services (OdxNet) will be used for access. | ||
| ==== AS [user]/[password] ==== | ==== AS [user]/[password] ==== | ||