[MCOL-3294] Allow moving a table to different schema with ALTER TABLE ... RENAME Created: 2019-05-03  Updated: 2023-11-14  Resolved: 2023-10-25

Status: Closed
Project: MariaDB ColumnStore
Component/s: DDLProc
Affects Version/s: 1.2.3
Fix Version/s: Icebox

Type: New Feature Priority: Major
Reporter: Kyle Joiner (Inactive) Assignee: Todd Stoffel (Inactive)
Resolution: Won't Fix Votes: 1
Labels: Compatibility

Issue Links:
Relates
relates to MCOL-130 ALTER TABLE does not support changing... Closed
relates to MCOL-3859 CLONE - Renaming table causes schema ... Closed
Epic Link: ColumnStore Compatibility Improvements

 Description   

Support moving a table to another schema with ALTER TABLE RENAME.

Currently:
MariaDB [(none)]> create database a1;
Query OK, 1 row affected (0.001 sec)

MariaDB [(none)]> create database a2;
Query OK, 1 row affected (0.000 sec)

MariaDB [(none)]> create table a1.t1 (id int)engine=columnstore;
Query OK, 0 rows affected (0.355 sec)

MariaDB [(none)]> use a1;
Database changed
MariaDB [a1]> alter table t1 rename a2.t1;
ERROR 1178 (42000): The storage engine for the table doesn't support Both tables must be in the same database to use RENAME TABLE


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