db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3350) SQL CAST always marks its type as nullable even if the expression to be cast is not nullable
Date Thu, 24 Jan 2008 20:28:34 GMT

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

Daniel John Debrunner updated DERBY-3350:
-----------------------------------------

    Attachment: derby3350_code_diff.txt

derby3350_code_diff.txt Patch that just shows the code changes, causes a number of tests to
fail due to the change in nullability.

> SQL CAST always marks its type as nullable even if the expression to be cast is not nullable
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3350
>                 URL: https://issues.apache.org/jira/browse/DERBY-3350
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0,
10.3.1.4, 10.3.2.1, 10.4.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>         Attachments: derby3350_code_diff.txt
>
>
> Can be exposed as a column's type in a ResultSet being nullable when in reality it can
never be null.
> Can impact performance as the SQL compiler can general optimal paths with correct nullability,
e.g. a non-null INTEGER expression does not need normalization if being stored in a non-null
INTEGER column, routine calling can be optimized for a RETURNS NULL ON NULL INPUT function
if the inputs are never null.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message