[DERBY-2879] CREATE TABLE AS <subquery> does not maintain the collation for character types.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 10.3.1.4, 10.4.1.3
• Fix Version/s: 10.3.1.4, 10.4.1.3
• Component/s: SQL
• Assignee: Mamta A. Satoor
• Reporter: Daniel John Debrunner
• Created: 27/Jun/07 14:18
• Updated: 02/Jul/07 18:05
• Resolved: 02/Jul/07 18:05

Description

create table t as select tablename from sys.systables with no data;

This creates a column TABLENAME with collation based upon the user schema, but the type of sys.systables.tablename has collation UCS_BASIC.

The required behaviour should be verified with the SQL standard (11.3 SR6), but since collation is an attribute of a type it seems logical that the collation is maintained by the create.

Fixing this to keep the collation of the system column will cause problems though as there would be no way to recreate this table through a regular create table, say if the schema is dumped and recreated using ddlutils.

I think this is critical as fixing it after a release would lead to a change in behaviour for applications.

Issue Links

• relates to: DERBY-2605 You can create BOOLEAN columns in 10.3
• relates to: DERBY-1478 Add built in language based ordering and like processing to Derby