Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

148 Chapter 10
Technical Articles
QUERY/iX Enhancements
Wildcard Character Limitations
Certain possible wildcard characters are used by QUERY for syntax
scanning and are limited in their usage. These special characters may
be utilized when the data values are delimited by double quotes (for
example, tilde, carat, comma, and parenthesis).
Figure 10-2
>FIND CUSTOMERS.CUSTOMER-NO=01540~
Tilde is a limited wildcard
EXPECTED A CONNECTOR OR 'END'
INVALID CONNECTOR OR TERMINATOR!
>FIND CUSTOMERS.CUSTOMER-NO="01540~"
Tilde enclosed in quotes works
8 ENTRIES QUALIFIED
>FIND CUSTOMERS.CUSTOMER-NO=01540"
Double-quote will not work…
EXPECTED A CONNECTOR OR 'END'
INVALID CONNECTOR OR TERMINATOR
>FIND CUSTOMERS.CUSTOMER-NO="01540"""
unless doubled in quotes and double-quote is wildcard
8 ENTRIES QUALIFIED
>FIND CUSTOMERS.CUSTOMER-NO=01540*
If asterisk is NOT the wildcard for this database, then no match unless the value 01540* is
in dataset.
0 ENTRIES QUALIFIED
B-Tree Limitations
QUERY will utilize the B-Tree functionality when possible for both
character and binary data types. The wildcard feature is only
implemented by TurboIMAGE/XL for character data types (X and U)
and not for binary data types. Neither has the Not Equal operator been
implemented for B-trees and so QUERY will continue to use the older
access methods (normally serial reads) for Not Equal retrievals. Note
that the LIST command always uses a serial read but will apply the
wildcard search character for relations.
When a database has the BTREEMODE1 flag set to OFF, QUERY will not
attempt to use the B-Tree functionality for Wildcard retrievals. This
condition is reported by all forms of the FORM command.