This shows you the differences between two versions of the page.
dev:sql:statements:set:home [2010/06/14 17:44] tdo |
dev:sql:statements:set:home [2016/06/28 22:38] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{page>:top_add&nofooter&noeditbtn}} | ||
- | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
- | ====== Omnidex SQL: SET STATEMENTS ====== | ||
- | ===== Description ===== | ||
- | |||
- | The following SET statements can modify the default Omnidex processing characteristics for a particular Omnidex connection. | ||
- | |||
- | Note that these SET statements can be issued by OdxSQL but are different that the SET commands used by OdxSQL. | ||
- | |||
- | | [[INSTANCE ]]| n | | | ||
- | | [[INTERRUPTS]] | <ON %%|%% OFF %%|%% API>] | | | ||
- | | [[NULL_INDICATORS]] | <ON %%|%% OFF %%|%% string> | | | ||
- | | [[OMNIDEX_DEBUG]] | <ON %%|%% OFF %%|%% profile> [FILE=filename]] | | | ||
- | | [[OPTIMIZATION]] | options | | | ||
- | | [[PSEUDOCOLUMNS]] | <ON %%|%% OFF> | desc | | ||
- | | [[QUALIFY_COUNTS]] | <PARENT %%|%% NOPARENT> | desc | | ||
- | | [[QUALIFY_MODE]] | <PARSER %%|%% ODXFIND %%|%% OX_FIND> | Sets how the QUALIFY statement will process criteria | | ||
- | | [[REDEFROWIDS]] | <ON %%|%% OFF> | desc | | ||
- | | [[REQUIRED_OPTIMIZATION]] | options] |desc | | ||
- | | [[SQL_LOGFILE]] | filename] |desc | | ||
- | | [[SQL_LOGGING]] | <ON %%|%% OFF> [WITH options] | desc | | ||
- | | [[SQL_SYNTAX]] | < ORACLE %%|%% OMNIDEX > | Allows some Oracle specific SQL functions to be used in Omnidex SQL statements. | | ||
- | | [[STATISTICS]] | <ON %%|%% OFF %%|%% filename>] |desc | | ||
- | | [[TIMEOUT]] | <seconds %%|%% OFF> | Sets how long an Omnidex QUALIFY or SELECT will process before timing out. | | ||
- | |||
- | |||
- | ===== Internal SET Commands ===== | ||
- | |||
- | <code> | ||
- | Internal | ||
- | x [AUTOPSEUDOCOLUMNS <ON | OFF>] | ||
- | x [AUTORECONNECT <ON | OFF>] | ||
- | x [AUTOSUBPROCESS <n | NONE> | ||
- | x [STATISTICS_COMMENT "string"] | ||
- | x [PREPROCESSOR <ON | OFF>] | ||
- | x [PROGRESS <ON | OFF>] | ||
- | x [MEMORY_BASELINE] | ||
- | x [FILE_BASELINE] | ||
- | </code> | ||
- | |||
- | ===== Level 2 Headline ===== | ||
- | |||
- | <code> | ||
- | SET DEBUG … | ||
- | SET OPTIMIZATION … | ||
- | SET REQUIRED_OPTIMIZATION | ||
- | SET CHAR … | ||
- | SET TIMEOUT … | ||
- | SET REDEFROWIDS … | ||
- | SET PSEUDOCOLUMNS … | ||
- | SET QUALIFY_MODE <ODXFIND | PARSER > | ||
- | SET AUTOPSEUDOCOLUMNS … | ||
- | SET PREPROCESSOR … | ||
- | SET SQL_LOGGING … | ||
- | SET SQL_LOGFILE … | ||
- | </code> | ||
- | |||
- | |||
- | The syntaxes of the SQL Logging SET commands are shown below: | ||
- | |||
- | set sql_logging <on | off> | ||
- | |||
- | This command activates SQL Logging for this process. By default, statements are logged to the $SQL_STATEMENTS file along with statistics about the execution of the command. The $SQL_STATEMENTS file is named “sqllog.tdf”, and is located in the same directory as the compiled environment file. This file is a standard tab-delimited file, and may be easily imported into other applications. The file may be flushed by simply removing the file; the file will be automatically recreated the next time logging is activated. | ||
- | |||
- | set sql_logfile <filename> | ||
- | |||
- | This command redirects the SQL logging for this process to a text file that only contains the statement, and does not contain any statistical information. If the file already exists, it will be appended to rather than overwritten. | ||
- | |||
- | |||
- | |||
- | {{page>:bottom_add&nofooter&noeditbtn}} |