MySQL administrator backups: "Compatibility mode", what exactly does this do?

In Mysql Administrator, when you backup, what is "Compatibility Mode"?

I am trying to compile backups created by webmin using the download tool available inside mysql admin . My data already has some inconsistencies (ticks, commas, etc., I think). I'm just not trying to bend (they may just appear in the future anyway). These kinks generate errors when I try to restore from backups.

Now, if I back up from webmin and then use the MySQL administrator to restore them, they fail. But if I create backups using the MySQL administrator and check "Compatibility mode", then go to the MySQL administrator (another instance) and restore ... it works!

According to MySQL, "Compatibility Mode":

Compatibility mode creates backup files that are compatible with older versions of MySQL Administrator.

Webmin, on the other hand, gives me the following compatibility options:

  • Ansi
  • MySQL 3.2.3
  • MySQL 4.0
  • PostgreSQL
  • Oracle
  • Microsoft SQL
  • DB2
  • Maxdb

What would you say is this best suited? My data set is very large, so it will take some time to experiment one after another (especially if thinking can exceed its cruelty).

Edit: it looks like it is doing ANSI, but I'm not 100% on it.

+6
mysql backup
source share
1 answer

Compatibility mode - a mode that helps to create exported data in different versions of MYSQL or other databases.

You see, some versions of MySQL had different commands that were used in different versions. So what kind of compatibility mode allows you to do is take a database and export SQL for compatibility with another version of MySQL. Thus, you can upgrade your MySQL 3 server to 4 - this compatibility mode allows you to export your database or individual tables to create an SQL file that can be imported into the server version of MySQL 4 (should also work in 5).

I use webmin, and I also run MySQL 5. I use the compatibility mode for MySQL 4 .... I avoid any other because I do not start these other databases.

As for the MySQL commands, which differed between MySQL 3.x and 4.x, I believe that there have been changes regarding how CURRENT_TIMESTAMP is translated from MySQL 3 to 4, and also MySQL 3 does not support encodings, according to this forum here: http://www.phpbuilder.com/board/showthread.php?t=10330692

+1
source share

All Articles