[jira] Resolved: (DERBY-2879) CREATE TABLE AS does not maintain the collation for character types.

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor resolved DERBY-2879.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0
                   10.3.1.1

Closing this issue.

Entered a new Jira entry for the code cleanup for duplication of code to get string representation from an int collation type. That jira entry is DERBY-2889

> CREATE TABLE AS <subquery> does not maintain the collation for character types.
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-2879
>                 URL: https://issues.apache.org/jira/browse/DERBY-2879
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.1.0, 10.3.1.1, 10.4.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Mamta A. Satoor
>            Priority: Critical
>             Fix For: 10.3.1.1, 10.4.0.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.