[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126786#comment-16126786
]
Bryan Pendleton commented on DERBY-6956:
----------------------------------------
To summarize: my opinion is that DERBY-836 and DERBY-2605 interacted to create
this problem.
DERBY-836 means that sometimes the maximum width is "illegal", and DERBY-2605
added the check that we should not create a new table with a column of
"illegal" maximum width.
Rick, what do you think?
> Create table as Select cannot copy Decimal columns
> --------------------------------------------------
>
> Key: DERBY-6956
> URL: https://issues.apache.org/jira/browse/DERBY-6956
> Project: Derby
> Issue Type: Bug
> Components: JDBC, SQL
> Affects Versions: 10.13.1.1
> Environment: Windows 7, DataGrip
> Reporter: Murat Cengiz
> Labels: newbie
>
> I create a test table with the following query:
> CREATE TABLE "DERBYTEST" ("STRINGCOLUMN" varchar(255), "INTEGERCOLUMN"
> integer, "SHORTCOLUMN" varchar(255), "LONGCOLUMN" bigint, "DOUBLECOLUMN"
> double, "FLOATCOLUMN" double, "DECIMALCOLUMN" decimal(31, 6), "BOOLEANCOLUMN"
> smallint, "DATECOLUMN" timestamp, "DATETIMECOLUMN" timestamp, "ID" integer,
> "LASTMODTIME" timestamp, PRIMARY KEY ("ID"))
> this query completes successfully
> I later try to copy the table with the following query:
> CREATE TABLE "DERBYTEST_TEMP" AS SELECT * FROM DERBYTEST WITH NO DATA
> This throws the following exception:
> [42X71][30000] Invalid data type 'DECIMAL(31, 6)' for column 'DECIMALCOLUMN'
> Everything works perfectly fine if I remove the decimal column.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
