[DERBY-2973] With collation TERRITORY_BASED, insert into table after changing type of column causes assert failure and loss of connection

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.3.1.4, 10.4.1.3
• Component/s: SQL
• Assignee: Mamta A. Satoor
• Reporter: Katherine Marsden
• Created: 24/Jul/07 17:03
• Updated: 17/Aug/07 22:29
• Resolved: 27/Jul/07 16:44

Description

ij(CONNECTION1)> create table d (id int not null, t_bigvarchar varchar(400), unique (id));
0 rows inserted/updated/deleted
ij(CONNECTION1)> create index t_bigvarchar_ind on d ( t_bigvarchar);
0 rows inserted/updated/deleted
ij(CONNECTION1)> alter table d alter t_bigvarchar set data type varchar(4096);
0 rows inserted/updated/deleted
ij(CONNECTION1)> insert into d (id, t_bigvarchar) values (1,'hello');
ERROR XJ001: Java exception: 'ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.SQLVarchartype of t
emplate column[0] = org.apache.derby.iapi.types.CollatorSQLVarchar: org.apache.derby.shared.common.sanity.AssertFailure'
.
ij(CONNECTION1)>

Issue Links

• is related to: DERBY-2656 Run suites.All against a collated database