Properties in the this category specify how Campaign handles string comparisons and empty fields in flat files, and the behavior of the macro
STRING_CONCAT.
The longNumericIdsAsText property specifies whether the
Campaign macro language will treat numeric IDs longer than 15 digits as text.
Set the value to yes to specify that numeric IDs longer than 15 digits will be treated as text.
Set the value to no to specify that numeric IDs longer than 15 digits are treated as numeric values (and thus might lose precision or uniqueness if truncated or rounded).
|
This setting is ignored if the partitions > partition[n] > dataSources > [data_source_name] > ForceNumeric property is set to TRUE for fields coming from this data source.
|
The stringConcatWithNullIsNull property controls the behavior of the
Campaign macro
STRING_CONCAT.
When the value is no,
STRING_CONCAT returns the concatenation of all of its non-
NULL properties; in this case,
STRING_CONCAT returns
NULL only if all of its inputs are
NULL.
The performCaseInsensitiveComparisonAs property specifies how
Campaign compares data values when the compareCaseSensitive property is set to
no (that is, during case-insensitive comparisons). This property is ignored if the value of compareCaseSensitive is
yes.
The upperAllowsDate property specifies whether the
UPPER database function allows a
DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the
Campaign server.
Set the value to yes if the database is SQL Server or Oracle. The
UPPER function in these databases allows a
DATE/DATETIME parameter.
Set the value to no if the database is
DB2®, Teradata, Sybase, or
Informix®. The
UPPER function in these databases does not allow a
DATE/DATETIME parameter.
The compareCaseSensitive property specifies whether the
Campaign data comparisons are sensitive to alphabetic case (UPPER vs. lower).
When the value is no,
Campaign ignores case differences when comparing data values and sorts textual data in a binary, case-insensitive manner. This setting is strongly recommended when English data is used.
When the value is yes,
Campaign distinguishes data values based on case differences, performing a true binary-value comparison of each character. This setting is strongly recommended when non-English data is used.
The lowerAllowsDate property specifies whether the
LOWER database function allows a
DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the
Campaign server.
Set the value to yes if the database is SQL Server or Oracle. The
LOWER function in these databases allows a
DATE/DATETIME parameter.
Set the value to no if the database is
DB2®, Teradata, Sybase, or
Informix®. The
LOWER function in these databases does not allow a
DATE/DATETIME parameter.
Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to
no. If a value of
yes is recommended for all data sources in use, set the value to
yes. Typically, only one database type is in use at a customer site, but there are some installations in which multiple database types are in use.
The substrAllowsDate property specifies whether the
SUBSTR/SUBSTRING database function allows a
DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the
Campaign server.
Set the value to yes if the database is Oracle or Teradata. The
SUBSTR/SUBSTRING function in these databases allows a
DATE/DATETIME parameter.
Set the value to no if the database is SQL Server,
DB2®, Sybase, or
Informix®. The
SUBSTR/SUBSTRING function in SQL Server,
DB2®, and Sybase does not allow a
DATE/DATETIME parameter.
Informix® SUBSTR does accept a
DATE parameter, but the
DATE is first converted to text, and the conversion changes the format. So
SUBSTR would return different results in the database compared with the
Campaign server, so the best practice is to set
substrAllowsDate to
no when the database is
Informix®.
The ltrimAllowsDate property specifies whether the
LTRIM database function allows a
DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the
Campaign server.
Set the value to yes if the database is SQL Server, Oracle, or Teradata. The
LTRIM function in these databases allows a
DATE/DATETIME parameter.
Set the value to no if the database is
DB2®, Sybase, or
Informix®. The
LTRIM function in these databases does not allow a
DATE/DATETIME parameter.
Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to
no. If a value of
yes is recommended for all data sources in use, set the value to
yes. Typically, only one database type is in use at a customer site, but there are some installations in which multiple database types are in use.
The rtrimAllowsDate property specifies whether the
RTRIM database function allows a
DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the
Campaign server.
Set the value to yes if the database is SQL Server, Oracle, or Teradata. The
RTRIM function in these databases allows a
DATE/DATETIME parameter.
Set the value to no if the database is
DB2®, Sybase, or
Informix®. The
RTRIM function in these databases does not allow a
DATE/DATETIME parameter.
The likeAllowsDate property specifies whether the
LIKE database function allows a
DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the
Campaign server.
Set the value to yes if the database is SQL Server or Oracle. The
LIKE function in these databases allows a
DATE/DATETIME parameter.
Set the value to no if the database is
DB2®, Teradata, Sybase, or
Informix®. The
LIKE function in these databases does not allow a
DATE/DATETIME parameter.
The fileAllSpacesIsNull property controls how
Campaign interprets an empty field in a mapped flat file by specifying whether an all-spaces value in a flat file should be considered to be a
NULL value.
When the value is yes, an all-spaces value is considered to be a
NULL value.
Campaign matches queries such as
<field> is null, but fails queries such as
<field> = "".
When the value is no, an all-spaces value is treated as a non-
NULL empty string.
Campaign matches queries such as
<field> = "", but fails
<field> is null.
Copyright IBM Corporation 2012. All Rights Reserved.
|