[MDEV-32367] Inproper reporting of ROCKSDB storage engine does not support generated columns Created: 2023-10-06  Updated: 2023-10-06

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - RocksDB
Affects Version/s: 11.0.2, 10.5.22
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Roy Bellingan Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Specifing the charset utf8mb4 will throw later an unrelated error

DROP TABLE keyword;
 
 
 
CREATE TABLE `keyword` (
 
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
 
  `search` varchar(255) NOT NULL,
 
  PRIMARY KEY (`id`),
 
  UNIQUE KEY `search` (`search`)
 
 
 
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
 
 
 
 
 
ALTER TABLE `keyword` ENGINE='ROCKSDB';

Using instead utf8mb3 it works fine.

Instead this is ok 

DROP TABLE keyword;
 
 
 
CREATE TABLE `keyword` (
 
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
 
  `search` varchar(255) NOT NULL,
 
  PRIMARY KEY (`id`)
 
 
 
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
 
 
 
 
 
ALTER TABLE `keyword` ENGINE='ROCKSDB';
 
ALTER TABLE `keyword` ADD KEY `search` (`search`);

And finally is setting a UNIQUE, if fails again

DROP TABLE keyword;
 
 
 
CREATE TABLE `keyword` (
 
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
 
  `search` varchar(255) NOT NULL,
 
  PRIMARY KEY (`id`)
 
 
 
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
 
 
 
ALTER TABLE `keyword` ENGINE='ROCKSDB';
 
ALTER TABLE `keyword` ADD UNIQUE KEY `search` (`search`);


Generated at Thu Feb 08 10:30:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.