[AUXWODBC], [ORACLE], [SYBASE]
use_long_query=0 or 1
0 means switched off, 1 means switched on. The default is 1 in AUXORACL and 0 otherwise.
For tables with multiple key fields SQL does not have an elegant method of selecting the record whose key is the next key in sequence. (Actually SQL2 defines a nice syntax for this allowing comparisons of the form
(field1,field2) > (value1,value2). Unfortunately existing databases do not support this syntax and it therefore is not used by the Gateway ADCs at present.)
Instead a where clause of the form WHERE field1 > value1 or (field1 = value1 and field2 > value2) must be used. Another way of expressing this condition is
WHERE field1 >= value1 and (field1 > value1 or field2 > value2).
If there are more than two keys the second form of the condition is longer than the first form, because in the first form each field is mentioned at most twice, but in the second form the first key must be mentioned as many times as there are key fields, the second key one fewer times and so on.
SQL databases may behave differently given the two forms of the condition. For example with Oracle there is no difference if there are only two keys, but if there are three, the shorter form of the condition stops the use_rownum feature from optimising the fetch time effectively. If you experience performance problems accessing tables with multi-part keys it is worth experimenting with this setting to see which gives better performance.
It should be noted that this option is partially incompatible with the use_subquery option. If both options are turned on the use_subquery option will only have an effect when exactly one key can vary.