[
https://issues.apache.org/jira/browse/DERBY-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677993#action_12677993
]
Knut Anders Hatlen commented on DERBY-4071:
-------------------------------------------
One possible "quick fix" may be to use the production jar files instead of the
debug jar files, as the production jars don't have the assertions.
I don't know if the assert failure exposes a bug or if it's just the assert
that is too strict, but this comment indicates that the one who added the
assert wasn't completely convinced that it was checking the right thing:
/**
Check that the columns in the row agree with the columns
in the template, both in number and in type.
<p>
XXX (nat) Currently checks that the classes implementing
each column are the same -- is this right?
**/
> 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
> Attachments: DerbyTest.java
>
>
> 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.
