The [Texis]
section of conf/texis.ini
affects Texis and
Vortex.
%LOGDIR%
variable, and thus the log dir for log file
settings that use this variable, e.g. [Texis] Vortex Log,
[Monitor] Log File, [Httpd] Transfer Log by default in
version 8. Thus changing this one setting (with log file settings
left default) will change where log files reside. Added in
version 8. See also Run Dir.
%RUNDIR%
variable, and thus the run dir for
run-time-only file settings that use this variable, e.g.
[Texis] Statistics Pipe, [Monitor] Lock File by default in
version 8. Thus changing this one settings (with run-time file
settings left default) will change where run-time files reside.
Added in version 8. See also Log Dir.
If nonzero (true), re-open/close log files for every use (e.g. every message), instead of keeping them open for the life of the process. This may allow system log rotators to rotate log files without restarting the monitor, vhttpd, or long-running Vortex script daemons, and potentially allows disk space to be recovered even if such a process is unresponsive. Affects monitor log, Vortex log, vhttpd and monitor web server transfer log, and vhttpd error log. Note that some of these log files may nonetheless be held open a non-trivial amount of time, if necessary. E.g. the monitor web server redirects Vortex scripts' standard error to the monitor log under Unix, so long-running or overlapping fetches of Vortex scripts run by the monitor web server may hold that log open (vhttpd does not do this).
Added in version 8.01.1711127229 20240322. See also [Monitor] Log Reopen (p.here), which defaults to this setting's value.
%SYSLIBPATH%
variable is unique to Lib Path, and refers to the OS-dependent
shared library load path.
Note that Lib Path refers to plugin libraries loaded after program startup by Texis, not linked libraries such as the C or math lib loaded by the OS at program startup. Added in version 4.01.1026200000 Jul 9 2002.
varchartostrlstsep
SQL setting
(here).
Added in version 5.01.1225870000 20081105.
multivaluetomultirow
SQL setting
(here). Added in version
5.01.1243980000 20090602.
blobz
fields, instead of the builtin routines. Uncompressed
data that is at least Blobz External Compress Min Size bytes
in size will be compressed with this command; smaller data (or if
Blobz External Compress Exe is unset) will use the default
internal gzip routine (or be stored as-is, whichever is
smaller). Blobz External Uncompress Exe must be set as well
if this setting is set, or data may not be readable once written.
Both commands must read input from stdin and write output to
stdout, and may contain space-separated arguments (quoted if
needed).
Note that using this setting may slow down table writes, as the
given executable may be run for any blobz
field written.
blobz
fields
that was previously commpressed with Blobz External Compress
Exe (here). Both commands must
read input from stdin and write output to stdout, and
may contain space-separated arguments (quoted if needed).
Note that using this setting may slow down table reads, as the
executable may be run for any blobz
field read.
blobz
fields. If source data is smaller, or Blobz
External Compress Exe is unset, the internal gzip routine
- or storage as-is - will be used instead. The default of 32 is a
compromise that avoids the overhead of running the executable for
small data that is unlikely to compress better than gzip
anyway, but still runs it for large data that might compress better.
A value of 0 would run it for all blobz
data written.
hexifybyte
SQL property
(here). Added in version 7.
Added in version 7.00.1372118000 20130624. Previous versions only tried the direct method.
Database and/or table to trace locks for (debugging). If either is set, locks trace messages will be saved to locks.lg in the appropriate database dir. Tracing will be limited to the database and/or table named.
Added in version 7.05.1449078000 20151202. Overridable by
validatebtrees
SQL property.
<trap>
directive and <vxcp trap>
statement. Not all
print-info flags supported on all platforms.
Added in version 7.06.1472335000 20160827.
While such escapes have no meaning currently, some may take on a specific new meaning in a future Texis release, if REX syntax is expanded. Thus using them in an expression now may unexpectedly (and silently) result in their behavior changing after a Texis update; hence the warning message. Expressions using such escapes should thus have them changed to the unescaped literal character.
If updating the code is not feasible, the warning may be silenced by
setting [Texis] Unneeded REX Escape Warning to no - at
the risk of silent behavior change at an upgrade. Added in version
7.06.1465574000 20160610. Overridden by
unneededrexescapewarning
SQL setting
(here).
compatibilityversion
8 and later,
on in version 7 and earlier DESC
flag use. If off, such ORDER BYs are consistent with others:
numerically ascending unless DESC
flag given (which would be
typical, to maintain descending-numerical-rank order). This setting
can be overridden by the legacyversion7orderbyrank
SQL
setting (here). Added
in version 7.06.1508871000 20171024.
Note that this setting may be removed in a future release, as its enabled behavior is deprecated. Its existence is only to ease transition of old code when upgrading to Texis version 8, and thus should only be used temporarily. Old code should be updated to reflect version 8 default behavior - and this setting removed from code - soon after upgrading.
<pwencrypt>
with no salt). Can be one of DES, MD5, SHA-256 or SHA-512. Added in version 8.
Note: For databases created with Texis version 7 or earlier, non-DES password hashes require upgrading the SYSUSERS table; this should happen automatically when a version 8+ database monitor starts (if [Monitor] Upgrade SYSTEM Tables is nonzero, the default in version 8). Changing the hash method for an existing password entry also requires explicitly updating the SYSUSERS entry (e.g. via ALTER USER ... SQL). If the SYSUSERS upgrade has not been performed, attempting to set a non-DES password hash will give the warning "SHA-512 password hash would be too long for current SYSUSERS schema in `...'; using DES instead", and DES will be used instead. A similar message may be given if creating a long (over 20 bytes) user name when the upgrade has not been performed.
<pwencrypt>
with no salt), for SHA algorithms.
Can be 1000 - 999999999. Added in version 8.
See also note for [Monitor] Default Password Hash Method,
here.
<vxcp compatibilityversion>
setting in Vortex for
details. Note that changing this setting may cause Vortex scripts
to need recompilation.
Other [Texis]
settings are specific to Texis Web Script (Vortex).
For details on these Vortex-specific settings,
see the "Configuration Settings" section of the Vortex manual.