[
https://issues.apache.org/jira/browse/DERBY-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480226
]
A B commented on DERBY-1620:
----------------------------
> I have done extensive testing, and I believe this patch finally fixes this
> bug.
That's great to hear. Can I ask what you mean by "extensive testing"? Did you
run the Derby regression suites at all? Do you have a list of queries that you
ran to verify everything is working as it should? And if so, is it possible to
add those queries to one of Derby's existing regression tests? This allows
other developers to ensure that everything will continue to work in the future.
If you do not feel like incorporating your test queries into an existing (or
new) regression test, then it would be great if you could at least post the
queries (ex. as an ij script) to this issue so that any other developers who
may be interested can add the test cases to the regression suite. It would, of
course, be wonderful if you were willing and able to do that yourself.
I as a committer am a bit hesitant to commit changes for which no new
regression tests have been added. There are exceptions, of course, but in this
particular case I think it would be great to have some new test cases running
every night to verify the fix. And if you've already done "extensive testing",
perhaps that means you have such test cases already written...?
> SQL CASE statement returns ERROR 42X89 when including NULL as a return value
> ----------------------------------------------------------------------------
>
> Key: DERBY-1620
> URL: https://issues.apache.org/jira/browse/DERBY-1620
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.1.6
> Environment: Windows XP
> Reporter: John Peterson
> Assigned To: John Peterson
> Priority: Minor
> Attachments: ConditionalNode.diff, ConditionalNode.diff,
> Derby_Community_Discussion.doc, derbyall_report.txt, sysinfo_and_example.txt
>
>
> This bug appears to be related to the DERBY-7 bug (NULLIF() function). When
> NULL is used during a CASE statement, Derby requires the NULL to be CAST to
> the appropriate type. This does not appear to meet the SQL 2003 Standard for
> the Case Expression (see attached Word document). See the attached Word
> document to view the Derby Community Discussion about this issue. See the
> attached .TXT to view the SYSINFO and to see an example of the steps to
> reproduce using IJ.
> Steps to Reproduce:
> ij>values case when 1=2 then 3 else NULL end;
> ERROR 42X89: Types 'INTEGER' and 'CHAR' are not type compatible. Neither
> type is assignable to the other type.
> Current Workaround:
> ij>values case when 1=2 then 3 else cast(NULL as INT) end;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
