New answers tagged

3

You can use replace into flag (--replace) and where condition (--where) while also omitting the create statement (-t): mysqldump -t --replace --where="id between 901 and 1000" my_db1 table my_table


0

Your table is probably corrupted. I would bet the indexes are the culprit here. You can try the "repair" command (myisam), or even better, to change the engine (and change it back again if you want): > ALTER TABLE t ENGINE=MyISAM; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id: 4 Current database: ...


1

Under MySQL 5.7, ROW_FORMAT=FIXED is no longer an option for the InnoDB Storage Engine. According to the MySQL 5.7 Documentation for innodb_default_row_format, these are values you can use for the table's row format: DYNAMIC, COMPACT, and REDUNDANT are allowed as default values COMPRESSED is not allowed to a default value, but you can explicitly use ...


3

First, I'll explain why DDL cannot execute during backup. The reason is that MySQL stores the definitions of relations (tables, indexes, etc) to MyISAM tables located at mysql subdirectory in version 5.6 or earlier (, therefore DDL should be prevented to execute during backup). Next, I'll answer your question. I assume that you use only innodb tables. (If ...



Top 50 recent answers are included