Lucent Technologies CentreVu, Руководство пользователя

Страница: 170 / 198

Advanced Report Design CentreVu CMS Custom Reports
Alternative Row Search Conditions
6-30
Using
Apostrophes
for Some
Database Item
Values
6
Some database items require that, if you hardcode values in a “where”
clause, you enclose the values in apostrophes ('), as shown in the following
example.
Select rows where: ROW_DATE > ’07/01/93’
Standard database items whose values you must enclose in apostrophes
are:
VDN (the value is a VDN number)
EXTENSION (the value is an extension number)
LOGID (the value is an agent login ID)
EQLOC (the value is a 9-digit trunk location number)
ROW_DATE (the value is a date in mm/dd/yy format)
CWC (the value is a call work code of 1 to 16 digits)
Also, any custom database items you define as CHAR or DATE columns in
INFORMIX are items whose hardcoded values you must enclose in
apostrophes.
For historical reports only, an alternative format for these database items
is:
Expression matches ’value’
In this type of clause,
matches
is the same as
=
. However, this type of
clause lets you use wildcard searches. That is, within the apostrophes, you
can use an asterisk (
*
) or a question mark (
?
).
The asterisk (
*
) matches any and all characters, including blanks and no
characters. Look at the following examples:
Select rows where: EQLOC matches ’01*’
This clause finds all rows where the EQLOC value begins with 01, which
would mean all trunks for module 01. Thus, 010012020, 010211110, and
011023100 are values that would match.
Select rows where: ROW_DATE matches ’*/01*’
This clause finds all rows where the ROW_DATE value has 01 as its dd (day
of the month). That is, the clause searches for the first day of each month.
Thus, 01/01/93, 04/01/93, and 10/01/92 are values that would match.
Note
Actually,
*/01*
would also find all dates, if they had passed, in the
year 2001 (for example, 01/22/01, 08/03/01, and 11/31/01).