This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dev:sql:statements:set:home [2010/06/14 17:47] tdo |
dev:sql:statements:set:home [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> | ||
| - | + | ====== Omnidex SQL: SET Statements ====== | |
| - | ====== Omnidex SQL: SET STATEMENTS ====== | + | {{page>:sql_bar&nofooter&noeditbtn}} |
| ===== Description ===== | ===== Description ===== | ||
| Line 9: | Line 9: | ||
| Note that these SET statements can also be issued interactively within OdxSQL or in an OdxSQL batch script. Note that OdxSQL also has SET commands that govern specific processing options of OdxSQL that are not allowed in an ODBC or JDBC application. | Note that these SET statements can also be issued interactively within OdxSQL or in an OdxSQL batch script. Note that OdxSQL also has SET commands that govern specific processing options of OdxSQL that are not allowed in an ODBC or JDBC application. | ||
| - | | [[INSTANCE ]]| n | | | + | | [[INSTANCE ]]| n | Changes the instance number when using multiple connections.| |
| | [[INTERRUPTS]] | <ON %%|%% OFF %%|%% API>] | | | | [[INTERRUPTS]] | <ON %%|%% OFF %%|%% API>] | | | ||
| | [[NULL_INDICATORS]] | <ON %%|%% OFF %%|%% string> | | | | [[NULL_INDICATORS]] | <ON %%|%% OFF %%|%% string> | | | ||
| Line 19: | Line 19: | ||
| | [[REDEFROWIDS]] | <ON %%|%% OFF> | | | | [[REDEFROWIDS]] | <ON %%|%% OFF> | | | ||
| | [[REQUIRED_OPTIMIZATION]] | options] | | | | [[REQUIRED_OPTIMIZATION]] | options] | | | ||
| - | | [[SQL_LOGFILE]] | filename] | | | + | | [[SQL_LOGFILE]] | filespec | | |
| - | | [[SQL_LOGGING]] | <ON %%|%% OFF> [WITH options] | | | + | | [[SQL_LOGGING]] | <ON %%|%% OFF %%|%% TEXT> %%[%%WITH options%%]%% | | |
| - | | [[SQL_SYNTAX]] | < ORACLE %%|%% OMNIDEX > | Allows some Oracle specific SQL functions to be used in Omnidex SQL statements. | | + | | [[SQL_SYNTAX]] | < ORACLE%%|%%OMNIDEX%%|%% SQLSERVER > | Allows some Oracle specific SQL functions to be used in Omnidex SQL statements or the SQLSERVER bracket syntax. | |
| | [[STATISTICS]] | <ON %%|%% OFF %%|%% filename>] | | | | [[STATISTICS]] | <ON %%|%% OFF %%|%% filename>] | | | ||
| | [[TIMEOUT]] | <seconds %%|%% OFF> | Sets how long an Omnidex QUALIFY or SELECT will process before timing out. | | | [[TIMEOUT]] | <seconds %%|%% OFF> | Sets how long an Omnidex QUALIFY or SELECT will process before timing out. | | ||
| - | ===== OdxSQL 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}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||