IBM Support

Local query processing occurs when an expression includes a zero length character literal

Troubleshooting


Problem

An expression in a model or report produces a character literal value which is a non-null string composed of zero characters ('').

Dynamic Query is aware of database vendors that do not follow the SQL standard and treat that value as being a null value.

For example, both ORACLE and Exasol document how their implementation does not follow the SQL standard.

When a zero length character literal is detected by Dynamic Query, it will result in query decomposition and more local processing.
 

Symptom

The following SQL statement defines a predicate which attempts to locate rows where the values in column C1 are a zero length string.

select C1 from MYTABLE where C1 = ''

When Dynamic Query detects that the underlying database does not follow the SQL standard, it will decompose the query and perform the comparison locally.

 

Cause

A vendor, such as ORACLE or Exasol does not follow the SQL standard with respect to zero length character literal value.

Resolving The Problem

Use character literal values which consist of at least a single space, for example ' '.   This is a character literal value of length one, and not zero which can be included in the SQL sent to a database.
 

Document Location

Worldwide

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"ARM Category":[{"code":"a8m50000000Cl5uAAC","label":"Reporting->Dynamic Query Mode and XQE"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
30 January 2021

UID

ibm16376256