[
https://issues.apache.org/jira/browse/DERBY-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James F. Adams updated DERBY-2605:
----------------------------------
Attachment: d2605_v1.stat
d2605_v1.patch
Attached is a patch that addresses the ability to create columns where the data
type of the column is currently for internal use or otherwise not exposed to
the user.
I added an isInternalTypeId method to TypeId and defined the following types as
being for internal use:
BOOLEAN
NATIONAL CHAR
NATIONAL LONGVARCHAR
NATIONAL VARCHAR
REF
TINYINT
USERDEFINED
NCLOB
CreateTableNode was updated to use this method to check the data type of each
column.
A new message was added.
A new test was added.
This patch does not address the situation with the VALUES statement desribed by
Army. I am wondering if the VALUES statement should even be allowed to create
rows with invalid decimal precision.
> You can create BOOLEAN columns in 10.3
> --------------------------------------
>
> Key: DERBY-2605
> URL: https://issues.apache.org/jira/browse/DERBY-2605
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Rick Hillegas
> Assigned To: James F. Adams
> Attachments: d2605_v1.patch, d2605_v1.stat
>
>
> The work on DERBY-64 seems to have opened up a wormhole by which you can
> create user tables with BOOLEAN columns. The following script shows how to do
> this:
> drop table foo;
> create table foo
> as select systemalias from sys.sysaliases with no data;
> rename column foo.systemalias to boolcol;
> alter table foo
> alter column boolcol null;
> select c.columndatatype
> from sys.syscolumns c, sys.systables t
> where t.tableid=c.referenceid
> and t.tablename='FOO';
> insert into foo( boolcol )
> values
> ( 0 ),
> ( 1 ),
> ( cast (null as int) )
> ;
> select * from foo;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
