Problem solve Get help with specific problems with your technologies, process and projects.

Oracle and the iSeries: Understanding nulls

This user discovered that in converting an application from using Oracle 8i to using DB2/400, Oracle behaves differently when concatenation nulls.

In converting an application from using Oracle 8i to using DB2/400, I discovered that Oracle behaves differently...

when concatenation nulls.

In Oracle, when you concatenate a string with a NULL, you get the original string.


 SQL> select title,firstname,
  2  title || firstname
  3  from employee;

---- ------------------------- -----------------------------
     Ed                        Ed

But, when doing the same thing on DB2/400, I found that concatenating anything to NULL returns NULL.

>  select title,firstname,
  title || firstname
  from employee;

title  firstName                  TITLE || FIRSTNAME
-      Ed                         -
 Therefore, Oracle acts differently than the iSeries on concatenating NULLs. On the iSeries, if either operand is NULL, the result is NULL. On Oracle, if either operand is NULL, the result is just the other operand. On the iSeries, we can use COALESCE (with an empty string) to produce the same result as Oracle.

> select title,firstname,
  coalesce(title,'') || firstname concatted
  from employee

title  firstName                  CONCATTED
-      Ed                         Ed

According to the IBM SQL Reference manual: Chapter 2 -- Language Elements -- Expressions: With the Concatenation Operator "If either operand can be null, the result can be null, and if either is null, the result is the null value. Otherwise, the result consists of the first operand string followed by the second."

This was last published in July 2005

Dig Deeper on Oracle on iSeries

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.