Innodb database backup considerations (solution caused by phpmyadmin) _ MySQL

Considerations for innodb database backup (solution caused by phpmyadmin) phpmyadmin

BitsCN.com

Because the default mysql engine is innodb, no engine is specified when phpmyadmin creates a table, that is, the default innodb is used. this engine is connected to ibdata1, ib_logfile0, and ib_logfile1 in the mysql/data/Directory. these three files add up to 40 Mb, and xampps cannot be packed in. when the database has innodb engine tables, deleting the three files [ibdata1, ib_logfile0, ib_logfile1] will affect the reading of all innodb engine tables. I think the problem is quite serious. what should I do if the user accidentally deletes it?

If accidentally deleted, it can only use the recovery method, it seems very complicated., can refer to this article http://www.bitsCN.com/article/45052.htm
I hope to help you.

How to solve this problem in the phpmyadmin table. in fact, the phpmyadmin table only saves some event operations and is not particularly important. In fact, you can also select MyISAM, so you can create and modify the phpmyadmin/examples/create_tables. SQL table, add the specified engine type before all the table creation statements, for example:

ENGINE = MyISAM default character set utf8 COLLATE utf8_bin;

After importing the data to mysql, you can copy the phpmyadmin library in the data/directory to another computer.

The attachment contains the modified phpmyadmin library file.

BitsCN.com