[MCOL-161] CREATE TABLE does not report what columns have invalid data types Created: 2016-06-22  Updated: 2022-11-05  Resolved: 2022-11-05

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: None
Fix Version/s: Icebox

Type: Bug Priority: Minor
Reporter: Justin Swanhart (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 3
Labels: None

Issue Links:
Relates
relates to MCOL-573 CS does not support reserved words as... Closed
Epic Link: ColumnStore Compatibility Improvements

 Description   

I have a complex CREATE TABLE:

create table fact (
i1 tinyint,
i2 smallint,
i3 mediumint,
i4 int,
i8 bigint,
i1u tinyint unsigned,
i2u smallint unsigned,
i3u mediumint unsigned,
i4u int unsigned,
i8u bigint unsigned,
d1 decimal(65),
d2 decimal(65,1),
d3 decimal(65,30),
d5 decimal(5,5),
f1 float,
f2 float(2,1),
f23 float(23,4),
f24 float(24,10),
f53 float(53,20),
r1 real,
r23 real(23,4),
r24 real(24,10),
r53 real(53,20),
dp1 double precision,
b0 bit(0),
b1 bit(1),
b64 bit(64),
d date,
dt datetime,
ts timestamp,
t time,
y2 year(2),
y4 year(4),
c0 char(0),
c1 char(1),
c2 char(255),
vc0 varchar(0),
vc1 varchar(1),
vc2 varchar(255),
vb0 varbinary(0),
vb1 varbinary(1),
vb2 varbinary(255),
bi0 binary(0),
bi1 binary(1),
bi2 binary(255),
bl0 blob(0),
bl1 blob(1),
bl2 blob(255),
tx0 text(0),
tx1 text(1),
tx2 text(255),
e1 enum('a'),
e2 enum(' ', 'a'),
e3 enum(' ', 'a', 'abc'),
s1 set('a'),
s2 set(' ', 'a'),
s3 set(' ', 'a', 'abc')
) ENGINE=COLUMNSTORE

1178 - The storage engine for the table doesn't support The syntax or the data type(s) is not supported by Columnstore. Please check the Columnstore syntax guide for supported syntax or data types.

For usability, CS should report the column (or columns) with invalid data types so that it can be corrected. This is a major usability problem.



 Comments   
Comment by Todd Stoffel (Inactive) [ 2022-11-05 ]

Item is out of date. Closing due to inactivity. If you feel this was done in error please open a new ticket.

Generated at Thu Feb 08 02:18:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.