[DERBY-1620] SQL CASE statement returns ERROR 42X89 when including NULL as a return value

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.3.1.4
• Component/s: SQL
• Environment: Windows XP
• Assignee: John Peterson
• Reporter: John Peterson
• Created: 01/Aug/06 14:53
• Updated: 16/Dec/07 19:56
• Resolved: 06/Jun/07 22:31

Description

This bug appears to be related to the DERBY-7 bug (NULLIF() function). When NULL is used during a CASE statement, Derby requires the NULL to be CAST to the appropriate type. This does not appear to meet the SQL 2003 Standard for the Case Expression (see attached Word document). See the attached Word document to view the Derby Community Discussion about this issue. See the attached .TXT to view the SYSINFO and to see an example of the steps to reproduce using IJ.

Steps to Reproduce:

ij>values case when 1=2 then 3 else NULL end;
ERROR 42X89: Types 'INTEGER' and 'CHAR' are not type compatible. Neither type is assignable to the other type.

Current Workaround:
ij>values case when 1=2 then 3 else cast(NULL as INT) end;

Issue Links

• is duplicated by: DERBY-3277 CREATE TABLE Test (n BIGINT);SELECT CASE WHEN n > -1 THEN n END FROM Test; FAILS
• relates to: DERBY-2986 Query involving CASE statement significantly slower in 10.3.1.4 than in 10.2.2.0