Bug #16199 dump which reads fine on 4.0.24 causes errors when read into a 4.1.15 server
Submitted: 4 Jan 2006 18:27 Modified: 4 Jan 2006 19:23
Reporter: Pete French Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.24 / 4.1.15 OS:FreeBSD (FreeBSD)
Assigned to: CPU Architecture:Any

[4 Jan 2006 18:27] Pete French
I have been sent the mysqldump output from a mysql 4.0.24 server which causes errors when I try and load it into a 4.1.15 server. Upon investigation the problem iis that the dump from the 4.0.24 contains lines like this:

/*!40101 SET NAMES  */;

(i.e. there is no characterset after the SET NAMES)

This causes the errors when the file is loaded into the 4.1.15 server. The file works fine when loaded into the original 4.0.24 server. I am not sure what operating system the 4.0.24 server is running on (it may be windows)

How to repeat:
try to load a file containing the lines /*!40101 SET NAMES  */; into a 4.1.15 server and observe the errors produced!

Suggested fix:
Either prevent mysqldump from producing such lines, or make the 4.1.15 server handle them without causing errors, like the 4.0.24 server does.
[4 Jan 2006 19:06] Pete French
I just got more information from the people who created the file, and it was done with mysqlfront and not mysqldump. But the fact remains that a dump which reads fine on the 4.0.25 server does not read on the 4.1.15 server, so there is still a problem here.
[4 Jan 2006 19:23] Hartmut Holzgraefe
Not a bug, at least not at our side

4.0 works fine with the following line

  /*!40101 SET NAMES  */;

as the !40101 comment indicates that this line is only relevant for versions 4.1.1 and above

4.1.15 is >4.1.1 so it tries to execute the command, which fails as the character set argument to SET NAMES is missing 

you should report that as a mysqlfront bug instead