TRACESQL directive sets an integer value that controls
the tracing of SQL calls made by a script. (Setting it to
on" or "
off" is the equivalent of 1 or 0,
respectively.) The lowest 4 bits are interpreted as a value from 0 to
15 that control SQL statement printing, with each value printing
everything at lower values too:
tsqlcommand line for testing (not recommended for production use)
The remaining higher bits are taken as flags to control other SQL tracing messages. Thus the following values can be bitwise ORed into the value:
As it is a directive,
<TRACESQL> must appear before the first
function in the script. SQL tracing can also be enabled at run time
sqlcp function (here), which overrides
this directive, and on the command line with the
option. Note that tracing functionality and values may change in
future releases, as this is a debugging directive. Values 0x04000,
0x08000 and 0x10000 were added in version 7.06.1517417000 20180131.
<if $del eq "y">
<sql "delete from books where id = $id"></sql>
<sql "update books set Text=$txt where id = $id"></sql>
<TRACESQL> directive was added in version 3.0.947100000 20000105.
<TRACESQL> to 2 or higher can produce large messages
for statements like the insertion of text fields.
-tracesql command line option