Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 17 Oct 2012 12:50:02 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <152003203.57338.1350478203630.JavaMail.jiratomcat@arcas>
In-Reply-To: <1602409079.45466.1346953387433.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (DERBY-5918) CREATE TABLE AS SELECT doesn't work
 on tables with BOOLEAN columns
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Hillegas updated DERBY-5918:
---------------------------------

    Attachment: derby-5918-01-aa-removeHurdle.diff

Attaching derby-5918-01-aa-removeHurdle.diff. This patch removes the false assertion by DataTypeDescriptor that users aren't allowed to create BOOLEAN columns. This fixes the bug. I am running regression tests now.


Touches the following files:

------------

M       java/engine/org/apache/derby/iapi/types/DataTypeDescriptor.java

Removes the disabling lie.

------------

M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/BooleanValuesTest.java

Adds a test case for this bug.

                
> CREATE TABLE AS SELECT doesn't work on tables with BOOLEAN columns
> ------------------------------------------------------------------
>
>                 Key: DERBY-5918
>                 URL: https://issues.apache.org/jira/browse/DERBY-5918
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>              Labels: derby_triage10_10
>         Attachments: derby-5918-01-aa-removeHurdle.diff
>
>
> You can't use CREATE TABLE AS SELECT from a table with a BOOLEAN column. This limitation was put in when CREATE TABLE AS SELECT was added. At that time you could not create user tables with BOOLEAN columns and we did not want people to be able to subvert that restriction by using CREATE TABLE AS SELECT from a system table with BOOLEAN columns. The following script shows this problem:
> connect 'jdbc:derby:memory:db;create=true';
> create table t1( a int );
> create table t2( a boolean );
> create table t3 as select * from t1 with no data;
> create table t4 as select * from t2 with no data;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira