[jira] Issue Comment Edited: (DERBY-3346) DatabaseMetaData.getIndexInfo returns the wrong nullabilty for column 4 NON_UNIQUE

["Daniel John Debrunner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564148#action_12564148 ] 

djd edited comment on DERBY-3346 at 1/30/08 11:40 AM:
------------------------------------------------------------------------

Fixed by Revision: 616853 for DERBY-2775

      was (Author: djd):
    Fixed by Revision: 616853 for DERBY-2275
  
> DatabaseMetaData.getIndexInfo returns the wrong nullabilty for column 4 NON_UNIQUE
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-3346
>                 URL: https://issues.apache.org/jira/browse/DERBY-3346
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, SQL
>    Affects Versions: 10.4.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>
> Derby's implementation of the NON_UNIQUE column for getIndexInfo() resolves to this expression:
> (CASE WHEN CONGLOMS.DESCRIPTOR.isUnique() THEN FALSE ELSE TRUE END) AS NON_UNIQUE
> The possible return values for this are TRUE or FALSE (this is internal SQL), which are both non-null constants,
> thus its type should be not nullable. A similar external SQL expression by itself does return the correct nullability,
> thus it seems to be a possible case where one node's nullability is affecting another. See DERBY-2775 and DERBY-3342. This like DERBY-3342 was found while fixing DERBY-2775.
> Working SQL with correct nullability:
> VALUES CASE WHEN 3=? THEN 1 ELSE 2 END

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