[MDEV-5441] Converting any_engine -> CONNECT deletes data Created: 2013-12-13  Updated: 2014-02-10  Resolved: 2014-02-10

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.6
Fix Version/s: 10.0.9

Type: Bug Priority: Critical
Reporter: Federico Razzoli Assignee: Olivier Bertrand
Resolution: Fixed Votes: 0
Labels: None


 Description   

IMO, this should work or be prohibited to prevent disasters. I tried InnoDB, MyISAM, CSV and the result is the same. Note that the default table type should be used, so the alter table should work in theory.

MariaDB [test]> CREATE TABLE t (c INT) ENGINE = InnoDB;
Query OK, 0 rows affected (0.51 sec)
 
MariaDB [test]> INSERT INTO t VALUES (1), (2), (3);
Query OK, 3 rows affected (0.07 sec)
Records: 3  Duplicates: 0  Warnings: 0
 
MariaDB [test]> ALTER TABLE t ENGINE = CONNECT;
Query OK, 0 rows affected, 2 warnings (0.46 sec)
Records: 0  Duplicates: 0  Warnings: 2
 
Warning (Code 1105): No table_type. Will be set to DOS
Warning (Code 1105): Wrong command in create, please contact CONNECT team
MariaDB [test]> SELECT * FROM t;
Empty set, 1 warning (0.00 sec)
 
Warning (Code 1105): Open(rb) error 2 on /usr/local/mariadb-10.0.5-linux-x86_64/data/./test/t.dos: No such file or directory



 Comments   
Comment by Federico Razzoli [ 2013-12-13 ]

In case there are plans to replace CSV with CONNECT, please note that MyISAM log tables can be converted into CSV log tables, and then be reconverted back. So, to be a full replacement, CONNECT should support such operations.

Comment by Olivier Bertrand [ 2014-02-10 ]

Was fixed in CONNECT version 1.02 released with MariaDB 10.0.8
(see MDEV-5440)

Generated at Thu Feb 08 07:04:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.