Browse Prior Art Database

CUA to Database Translation for Generic Search Characters

IP.com Disclosure Number: IPCOM000110124D
Original Publication Date: 1992-Oct-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 3 page(s) / 82K

Publishing Venue

IBM

Related People

Okruw, SK: AUTHOR

Abstract

The standard characters specified for use as "wildcard" search characters under the Common User Access* (CUA*) guidelines differ from those employed in IBM's strategic database product DB2*. It therefore becomes necessary to provide a mechanism for translating the CUA-defined characters to the database defined form without any loss in translation for the search to be performed by the user.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

CUA to Database Translation for Generic Search Characters

       The standard characters specified for use as "wildcard"
search characters under the Common User Access* (CUA*) guidelines
differ from those employed in IBM's strategic database product DB2*.
It therefore becomes necessary to provide a mechanism for translating
the CUA-defined characters to the database defined form without any
loss in translation for the search to be performed by the user.

      The CUA wildcard tokens are "*" to denote a string of zero to
any length and "?" to denote a single character.  The corresponding
tokens for DB2 are "%" and "_", respectively.

      Also CUA standards do not provide "escape" capabilities for
these wildcard characters.  (Escape capability is the ability to
denote that a wildcard character entered in a search is to be
interpreted as the character itself and not as a wildcard character,
i.e., provide the capability to search for the wildcard character
value in the database).  To accomplish this, the wildcard token "*"
will be used as an escape character for itself and also for the other
wildcard token "?".

      The disclosed mechanism for the translation of CUA-defined
search characters to the appropriate database search characters and
the provision of "escape" capabilities for the CUA search characters
will have the following characteristics:
1.  Create an output field of the variable-length string type.  This
is the field containing the translated characters to be used in the
query of the database.
2.  Initialize an integer field n to 1.  This is used to keep track
of which character in the input field (the string of characters
entered on the screen by the user) is being examined for translation.
3.  Initialize an integer field x to 0.  This field is used to track
the number of characters written to the output area.
4.  Set the DB2 escape character equal to the CUA wildcard '*'.
5.  If there is no input for a field, presume that any character
string in the column will satisfy the query; therefore,
   a)  write a  "%" to output area,
   b)  set length portion of the output va...