db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian d'Heureuse (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-7) Bug in NULLIF Function
Date Wed, 22 Dec 2004 15:29:11 GMT
     [ http://nagoya.apache.org/jira/browse/DERBY-7?page=comments#action_56977 ]
Christian d'Heureuse commented on DERBY-7:

Sorry, ignore my previous comment. I had mistaken nullif() with isnull/coalesce().

The expression
 values nullif(1,1)
should return the value
 cast(null as int)

In sqlgrammar.jj there is the following comment:
// "NULLIF(L, R)" is the same as "L=R ? CAST(NULL AS CHAR(1)) : L"

I think the problem is:
 thenExpression = CAST(NULL AS CHAR(1)) = type CHAR
 elseExpression = L = type INT
==> CHAR and INT are not compatible.

To solve this problem, the data type of L (leftExpression) could be used to build the NULL
constant node, instead of CHAR(1).

> Bug in NULLIF Function
> ----------------------
>          Key: DERBY-7
>          URL: http://nagoya.apache.org/jira/browse/DERBY-7
>      Project: Derby
>         Type: Bug
>   Components: SQL
>     Versions:
>     Reporter: Tulika Agrawal
>     Priority: Minor

> Reporting for Christian d'Heureuse, filed on derby-dev list.
> The NULLIF built-in function of Cloudscape beta seems to accept
> only string values.
> Examples:
>  values nullif('a','b');
>  --> OK
>  values nullif(1,2);
>  --> Error message: "ERROR 42X89: Types 'CHAR' and
>      'INTEGER' are not type compatible. (Neither type
>      is assignable to the other type.)"

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message