[MDEV-5650] FLUSH FOR EXPORT: missing error if engine does not support it Created: 2014-02-11  Updated: 2014-02-11  Resolved: 2014-02-11

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

Type: Bug Priority: Major
Reporter: Federico Razzoli Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

On MySQL 5.6:

MySQL [test]> CREATE TABLE t (c INT) ENGINE=MyISAM;
 
Query OK, 0 rows affected (0.09 sec)
 
 
 
MySQL [test]> FLUSH TABLES t FOR EXPORT;
 
ERROR 1031 (HY000): Table storage engine for 't' doesn't have this option

On MariaDB 10.0.8:

MariaDB [test]> CREATE TABLE t (c INT) ENGINE=MyISAM;
 
Query OK, 0 rows affected (0.07 sec)
 
 
 
MariaDB [test]> FLUSH TABLES t FOR EXPORT;
 
Query OK, 0 rows affected (0.00 sec)

If FOR EXPORT behaves like in MySQL, an error should be issued...

 Comments   
Comment by Elena Stepanova [ 2014-02-11 ]

In MariaDB 10.0, MyISAM supports FLUSH .. FOR EXPORT.

/*
Storage engine supports table export using the
FLUSH TABLE <table_list> FOR EXPORT statement
(meaning, after this statement one can copy table files out of the
datadir and later "import" (somehow) in another MariaDB instance)
*/

Comment by Sergei Golubchik [ 2014-02-11 ]

I've amended the manual as well, it does not say that FLUSH …FOR EXPORT is InnoDB only.

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