This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
appendix:reference:envvar:uses [2011/03/15 17:38] els |
appendix:reference:envvar:uses [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| ==== Uses of Environment Variables and Shell Commands ==== | ==== Uses of Environment Variables and Shell Commands ==== | ||
| - | Environment variables and shell commands can be used in several locations in the Omnidex product, as shown in the following list: | + | Environment variables and shell commands can be used in many locations in the Omnidex product. In most cases, environment variables and shell commands can be used whenever a filename can be referenced in the Omnidex product. Environment variables and shell commands can also be used in CREATE statements that generate Omnidex Environment Files. The following is a list of common uses for environment variables and shell commands within the product: |
| === Connection Strings === | === Connection Strings === | ||
| - | Environment variables and shell commands can be use in each portion of the connection string. Consult the documentation on [[dev:connections:home|Connection Strings]]. | + | Connection strings are used in many places within the Omnidex product. Environment variables and shell commands can be use in each portion of the connection string. Consult the documentation on [[dev:connections:home|Connection Strings]]. |
| - | === CREATE DATABASE === | + | === CREATE DATABASE Statement === |
| Environment variables and shell commands can be used in the PHYSICAL clause to affect the service name for Oracle, and to affect the FILEDSN for SQL Server and ODBC (including MySQL). | Environment variables and shell commands can be used in the PHYSICAL clause to affect the service name for Oracle, and to affect the FILEDSN for SQL Server and ODBC (including MySQL). | ||
| Line 31: | Line 31: | ||
| Environment variables and shell commands can be used for the INDEX_DIRECTORY for all databases. | Environment variables and shell commands can be used for the INDEX_DIRECTORY for all databases. | ||
| - | === CREATE TABLE === | + | === CREATE TABLE Statement === |
| Environment variables and shell commands can be used for PHYSICAL clause on Raw Data Files. | Environment variables and shell commands can be used for PHYSICAL clause on Raw Data Files. | ||
| - | === EXPORT === | + | === EXPORT Statement === |
| Environment variables and shell commands can be used for target filename for the EXPORT statement. | Environment variables and shell commands can be used for target filename for the EXPORT statement. | ||
| + | |||
| + | === ATTACH Statement === | ||
| + | |||
| + | Environment variables and shell commands can be used for Omnidex Standalone Table filenames in the ATTACH statement. | ||
| + | |||
| + | === UPDATE INDEXES Statement === | ||
| + | |||
| + | Environment variables and shell commands can be used for the log directory named in the LOG_DIR option of the UPDATE INDEXES statement. | ||
| + | |||
| + | === $RETRIEVE_FILE Function === | ||
| + | |||
| + | Environment variables and shell commands can be used in the filename parameter of the $RETRIEVE_FILE SQL function. | ||
| \\ | \\ | ||