Bug #35382 Lock tables does not work - not even while using FLUSH TABLES WITH...
Submitted: 18 Mar 2008 8:23 Modified: 4 Nov 2008 13:57
Reporter: Magnus MF Rolf Email Updates:
Status: Closed Impact on me:
Category:MySQL Query Browser Severity:S1 (Critical)
Version:1.2.12 OS:Microsoft Windows (lock tables does not work)
Assigned to: Mike Lischke CPU Architecture:Any
Tags: flush tables with read lock, lock tables, Mysql Query Browser, no lock at all

[18 Mar 2008 8:23] Magnus MF Rolf
While using MySQL Query Browser, version 1.2.10 (very latest version) and issuing a 'FLUSH TABLES WITH READ LOCK' to prevent other connections / users to write to the binary lock ahead to process a full backup (MyIsam only database); the lock is not applied. 
Users and web-connections are still to read and WRITE to the database tables. By doing this it is not possible to create a proper backup and determine the binary log position. Any commited write still changes the binary log position (visual by issuin a SHOW MASTER STATUS command)

(1) stop web-server connection (prevent other user interference)
(2) using MySQL command-line client (native mysql) and issuing the sequence of commands there (Flush tables with read lock; make backup; show master status; copy log-file name and position)

How to repeat:
just try issuing a lock command within the query-browser and try to update a "locked" table by using annother mysql client (or browser connection)

I do not think you really will smile :-)

Suggested fix:
PLEASE do let the LOCK work!

PS When using the backup/restore utility from within Query Browser the lock does work - I do think a standard mysql client command is used to perform the task
[18 Mar 2008 8:59] Valeriy Kravchuk
Thank you for a problem report. Verified just as described.
[4 Nov 2008 13:57] Mike Lischke
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 bug fix. More information about accessing the source trees is available at