You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dyre Tjeldvoll (JIRA)" <de...@db.apache.org> on 2006/09/28 16:24:53 UTC
[jira] Commented: (DERBY-729) Scalar time and date functions return
0 instead NULL when argument is NULL
[ http://issues.apache.org/jira/browse/DERBY-729?page=comments#action_12438447 ]
Dyre Tjeldvoll commented on DERBY-729:
--------------------------------------
Hi Bernt,
I have looked at the patch, and I think it looks solid, and the test seems to cover the relevant cases.
Could there be existing applications that somehow rely on the incorrect behavior? If so, should there perhaps be a release note?
+1 to commit
> Scalar time and date functions return 0 instead NULL when argument is NULL
> --------------------------------------------------------------------------
>
> Key: DERBY-729
> URL: http://issues.apache.org/jira/browse/DERBY-729
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.1.3.2, 10.2.1.5
> Reporter: Bernt M. Johnsen
> Assigned To: Bernt M. Johnsen
> Fix For: 10.3.0.0
>
> Attachments: DERBY-729-1.diff, DERBY-729-1.stat
>
>
> The scalar time and date functions should return NULL when argument is NULL.
> Sample ij run that reproduces the bug
> ij> create table dt (ts timestamp);
> 0 rows inserted/updated/deleted
> ij> insert into dt values ({ts '2005-11-28 14:49:40'}), (NULL);
> 2 rows inserted/updated/deleted
> ij> select * from dt;
> TS
> --------------------------
> 2005-11-28 14:49:40.0
> NULL
>
> 2 rows selected
> ij> select {fn hour(ts)} from dt;
> 1
> -----------
> 14
> 0
> might be a problem with other scalar functions too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira