[
https://issues.apache.org/jira/browse/DERBY-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680529#action_12680529
]
Bryan Pendleton commented on DERBY-4071:
----------------------------------------
Hi Dag, thanks for the very thorough writeup and notes. Your analysis makes a
lot of sense to me.
I'm wondering: with your patch, do we still need the DERBY-3880 patch? That is,
what happens if you apply your patch, and *undo* the DERBY-3880 patch? Do the
DERBY-4071 and DERBY-3880 test cases then pass? Or do we actually need both
patches to get the column references in the HAVING clause expressions to be
mapped correctly?
> AssertFailure when selecting rows from a table with CHARACTER and VARCHAR
> columns
> ---------------------------------------------------------------------------------
>
> Key: DERBY-4071
> URL: https://issues.apache.org/jira/browse/DERBY-4071
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.4.2.0
> Reporter: Aaron Digulla
> Assignee: Dag H. Wanvik
> Attachments: derby-4071.diff, derby-4071.stat, DerbyTest.java,
> trialPatch.diff
>
>
> When running a complex query on this table:
> [code]
> Create table DEMO.TEST (
> CHR CHARACTER(26) ,
> VCHR VARCHAR(25) )
> [code]
> then I get this exception:
> AssertFailure: ASSERT FAILED col1.getClass() (class ...SQLChar) expected to
> be the same as col2.getClass() (class ....SQLVarchar)' was thrown while
> evaluating an expression.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
