[
https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570748#action_12570748
]
Kathey Marsden commented on DERBY-3310:
---------------------------------------
VirtualColumnNode has this comment
/* A VirtualColumnNode contains a pointer to the immediate child result
* that is materializing the virtual column and the ResultColumn
* that represents that materialization.
*/
private ResultSetNode sourceResultSet;
private ResultColumn sourceColumn;
The DERBY-2775 change overrode the setType from ValueNode:
public void setType(DataTypeDescriptor dataTypeServices) throws
StandardException
{
this.dataTypeServices = dataTypeServices;
}
with
public void setType(DataTypeDescriptor dtd) throws StandardException
{
sourceColumn.setType(dtd);
}
Doesn't this end up incorrectly end up affecting the child result, changing it
from
SQLInteger to SQLLongInt?
> 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.
