[jira] Updated: (DERBY-729) Scalar time and date functions return 0 instead NULL when argument is NULL

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-729:
-------------------------------------

    Attachment: releaseNote.html

I'm attaching an attempt at a release note.
It's a little contrived, maybe it'd be clear enough with just the summary and application change headings?



> Scalar time and date functions return 0 instead NULL when argument is NULL
> --------------------------------------------------------------------------
>
>                 Key: DERBY-729
>                 URL: https://issues.apache.org/jira/browse/DERBY-729
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.1.3.2, 10.2.1.6
>            Reporter: Bernt M. Johnsen
>         Assigned To: Bernt M. Johnsen
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-729-1.diff, DERBY-729-1.stat, releaseNote.html
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.