[
https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568679#action_12568679
]
Kathey Marsden commented on DERBY-3310:
---------------------------------------
I think then we get back to my question of whether both template and row data
should be SQLInteger or both should be SQLLongint at the time of the sort.
BTW this is the trace from the point where we now change the type of the
sourceColumn from INTEGER NOT NULL to BIGINT.
I think I need to better understand the VirtualColumnNode change and why it was
made.
Thread [main] (Suspended (breakpoint at line 284 in VirtualColumnNode))
VirtualColumnNode.setType(DataTypeDescriptor) line: 284
ResultColumnList.copyTypesAndLengthsToSource(ResultColumnList) line:
1645
InsertNode.bindStatement() line: 426
GenericStatement.prepMinion(LanguageConnectionContext, boolean,
Object[], SchemaDescriptor, boolean) line: 314
GenericStatement.prepare(LanguageConnectionContext, boolean) line: 88
GenericLanguageConnectionContext.prepareInternalStatement(SchemaDescriptor,
String, boolean, boolean) line: 768
EmbedStatement40(EmbedStatement).execute(String, boolean, boolean, int,
int[], String[]) line: 607
EmbedStatement40(EmbedStatement).execute(String) line: 556
ij.executeImmediate(String) line: 330
utilMain.doCatch(String) line: 508
utilMain.runScriptGuts() line: 350
utilMain.go(LocalizedInput[], LocalizedOutput, Properties) line: 248
Main.go(LocalizedInput, LocalizedOutput, Properties) line: 215
Main.mainCore(String[], Main) line: 181
Main.main(String[]) line: 73
ij.main(String[]) line: 59
> 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
> Priority: Minor
> Attachments: cast-repro.sql
>
>
> 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.
