Bug #2242 mysqldump LOCK/UNLOCK bug
Submitted: 31 Dec 2003 0:43 Modified: 6 Jan 2004 4:26
Reporter: Minor Hsu Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:3.23.58 OS:Linux (linux)
Assigned to: MySQL Verification Team CPU Architecture:Any

[31 Dec 2003 0:43] Minor Hsu 
Description:
=========== the code in mysqldump.c ============ 
if (lock_tables)
  mysql_query(sock,"UNLOCK_TABLES");
================================================
the "UNLOCK_TABLES" should be "UNLOCK TABLES"

How to repeat:
=========== the code in mysqldump.c ============ 
if (lock_tables)
  mysql_query(sock,"UNLOCK_TABLES");
================================================
the "UNLOCK_TABLES" should be "UNLOCK TABLES"

Suggested fix:
=========== the code in mysqldump.c ============ 
if (lock_tables)
  mysql_query(sock,"UNLOCK_TABLES");
================================================
the "UNLOCK_TABLES" should be "UNLOCK TABLES"
[31 Dec 2003 6:56] Dean Ellis 
Occurs in dump_all_tables_in_db() and dump_selected_tables().
[3 Jan 2004 10:43] MySQL Verification Team 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fix should come in 4.0.18