[MCOL-337] support full spec for character set clauses Created: 2016-09-28  Updated: 2021-09-10  Resolved: 2020-06-22

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: 1.0.3
Fix Version/s: 1.5.2

Type: New Feature Priority: Major
Reporter: David Thompson (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 3
Labels: None

Issue Links:
Blocks
is blocked by MDEV-21504 Collation: Create shared library for ... Closed
Epic Link: ColumnStore Compatibility Improvements

 Description   

columnstore does not support column level character set specification and the collation clause. For example the following fails:
CREATE TABLE table1 ( name char(3) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL DEFAULT '') ENGINE=Columnstore

A workaround is to specify at the table level and drop the collate option:
CREATE TABLE table1 ( name char(3) NOT NULL DEFAULT '')default CHARACTER SET latin1 engine=columnstore;

Originally reported here: https://mariadb.com/kb/en/mariadb/character-set-problem-in-columnstore



 Comments   
Comment by Daniel Lee (Inactive) [ 2020-06-22 ]

Build verified: 1.5.2-1 (community edition, b33685)

Comment by Jean-Bernard Jansen [ 2020-09-18 ]

Why is it closed ? The code is nowhere to be found in the repo.

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