[DERBY-3310] ASSERT in MergeSort.checkColumnTypes() disallow legal type conversions

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.1.3, 10.5.1.1
• Component/s: SQL
• Issue & fix info: Patch Available
• Bug behavior facts: Regression
• Assignee: Katherine Marsden
• Reporter: Dyre Tjeldvoll
• Created: 09/Jan/08 16:05
• Updated: 21/Jan/11 17:51
• Resolved: 20/Mar/08 04:52

Description

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'.

Issue Links

• is related to: DERBY-3221 "java.sql.SQLException: The conglomerate (-5) requested does not exist." from Derby 10.3.1.4 embedded within Eclipse 3.3 and RAD 7.0
• relates to: DERBY-3395 'An ON clause associated with a JOIN operator is not valid.' failure with 10.3.2.1 passes with 10.2
• relates to: DERBY-2775 DataTypeDescriptor should be immutable so that multiple ValueNode referring to the same DTD do not have unexpected state changes.
• relates to: DERBY-3494 Move the setup of NormalizeResultSetNode into the NormalizeResultSetNode