You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "David Myers (JIRA)" <ji...@apache.org> on 2012/09/07 10:46:07 UTC

[jira] [Comment Edited] (DERBY-5918) CREATE TABLE AS SELECT doesn't work on tables with BOOLEAN columns

    [ https://issues.apache.org/jira/browse/DERBY-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450465#comment-13450465 ] 

David Myers edited comment on DERBY-5918 at 9/7/12 7:45 PM:
------------------------------------------------------------

I've just noticed that you have set this for version 10.10

I found this error in 10.9

I also note that from Riks comment that the Boolean data type was added fairly recently, I don't know precisely when. Should this bug push an update through to the previously available versions that included the Boolean type?

Edit: located the 'add boolean data type' jira bug: https://issues.apache.org/jira/browse/DERBY-4716

It seems the boolean type was first added in 10.6.1

David
                
      was (Author: dmyers):
    I've just noticed that you have set this for version 10.10

I found this error in 10.9

I also note that from Riks comment that the Boolean data type was added fairly recently, I don't know precisely when. Should this bug push an update through to the previously available versions that included the Boolean type?
                  
> 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
>
> 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