[
https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571624#action_12571624
]
Daniel John Debrunner commented on DERBY-3310:
----------------------------------------------
> Do you think this is a sufficient incremental improvement to resolve the
> regression?
In my opinion not at the moment, I'm uncomfortable with fixes that can't be
explained. At the moment it's a case
of :
- if I do this then it appears to work but I don't know why.
It's good that you've found the likely source of the problem, but it's just a
starting point.
I'll spend some time trying to understand what that method is trying to do, it
probably has to
do with some comments in ResultSetNode.genNormalizeResultSetNode:
* Put a NormalizeResultSetNode on top of the specified ResultSetNode.
* ColumnReferences must continue to point to the same ResultColumn, so
* that ResultColumn must percolate up to the new PRN.
Not sure what that means exactly, but it seems related.
> ASSERT in MergeSort.checkColumnTypes() disallow legal type conversions
> ----------------------------------------------------------------------
>
> Key: DERBY-3310
> URL: https://issues.apache.org/jira/browse/DERBY-3310
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.4.0.0
> Reporter: Dyre Tjeldvoll
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: cast-repro.sql, derby-3310_try1_diff.txt
>
>
> The following code
> CREATE TABLE U (SNAME VARCHAR(32000), TNAME VARCHAR(32000), C1 BIGINT);
> -- This triggers an ASSERT (because 2 is INTEGER and not BIGINT)
> INSERT INTO U(SNAME, TNAME, C1) SELECT DISTINCT SCHEMANAME, TABLENAME, 2
> FROM SYS.SYSTABLES T JOIN SYS.SYSSCHEMAS S ON T.SCHEMAID = S.SCHEMAID;
> gives
> ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class
> org.apache.derby.iapi.types.SQLInteger) expected to be the same as
> col2.getClass() (class org.apache.derby.iapi.types.SQLLongint):
> org.apache.derby.shared.common.sanity.AssertFailure'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
