Bug #57779 Executing a Statement results in error message "No such table: changes"
Submitted: 27 Oct 2010 18:28 Modified: 27 Apr 2011 16:52
Reporter: Daniel Seif Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.31 GA OS:Linux (Ubuntu 10.04 LTS)
Assigned to: CPU Architecture:Any

[27 Oct 2010 18:28] Daniel Seif
Description:
After working for a while, performing various tasks (selecting, inserting, updating), it happens, that a newly entered statement does not get executed.

In the Output (Tab Actions) the error

    "Error: no such table: changes"

occurs and the previous SELECT result is displayed.

Closing the database connection and opening it with a new tab resolves the problem temporarily. A second tab with the same database connection works flawlessly.

How to repeat:
Work with the workbench.
[28 Oct 2010 0:01] MySQL Verification Team
I couldn't repeat are you able to provide a step by step instruction so it can be repeatable?. Thanks in advance.
[30 Oct 2010 8:55] Daniel Seif
Unfortunately I can see no regularity with which this happens. Sometimes I can work with the SQL Editor for hours without any problem, let it rest for a few minutes and the error occurs.

Sometimes it just happens suddenly: I execute a select, look at the result, change the select, execute it and I see the previous select.
[9 Dec 2010 0:59] MySQL Verification Team
Could you please try version 5.2.31. Thanks in advance.
[17 Dec 2010 14:51] Daniel Seif
With 5.2.31 the error still occurs
[4 Jan 2011 16:24] Steve Wollkind
I see this behavior with some regularity as well.  It seems only to occur after leaving the workbench and db connection open for quite some time, like over the weekend.  Perhaps the connection has been lost/closed somehow in the meantime.  I'm not quite sure.  I have to close the connection tab and open a new one to proceed.
[13 Apr 2011 11:24] Valeriy Kravchuk
Please, check if this problem still happens with a newer version, 5.2.33.
[27 Apr 2011 7:34] Daniel Seif
The error didn't occur on 5.2.33 for a while. It seems as if the problem is solved.
[27 Apr 2011 16:52] Valeriy Kravchuk
Not repeatable with 5.2.33 it seems.
[29 Apr 2011 8:16] [ name withheld ]
The problem still occurs in 5.2.33.

Just installed Workbench 5.2.33 64Bit Build (rev 7508) for Ubuntu 10.04 LTS and on the first startup and the first query I encountered this problem (was a describe statement, if that helps).
[15 Jul 2011 20:03] Steve Wollkind
I just had this happen in 5.2.34, and right in the middle of my using it.  Previously I only encountered this behavior after leaving the application open over a weekend, etc.
[15 Jul 2011 20:05] Steve Wollkind
I should point out that while the OS listed in the bug is Ubuntu, I've been seeing this on the Mac OS X version as long as I've worked with it.
[19 Jul 2011 7:29] [ name withheld ]
I experience this problem whenever I have two or more instances of MySQL Workbench running at the same time. The instance I have started last will work as expected, all other instances will issue "Error: no such table: changes" error. (Tested on Ubuntu 10.04 LTS 64Bit, MySQL WB 5.2.34)
[21 Jul 2011 22:11] Sergio Bobillier
This bug is still present in 5.2.34 rev 7780 (Ubuntu 11.04). After leaving the Workbench idle for a while any statement executed will cause the workbench to respond with the "No such table: changes" message.

If you click the Reconnect to DBMS button on the toolbar to try and get the connection tab responsive again the whole Workbench freezes.
[28 Jul 2011 15:19] Shauna Gordon
This still happens to me in 5.2.34 rev 7780 (Ubuntu 11.04).

How I got it:

Open Workbench and connect to a database (in my case, it was a local one).
Leave it open for a while, but don't do anything with it.
Open a new instance of Workbench, no need to connect to any database, can even close this new instance.
Try to run a query in the first instance/connection.

After some playing around, I was also able to get it to consistently error with "Could not connect to database" by opening a second instance of Workbench (which I think may still be related to this issue), even without leaving the first open for very long. The second instance also reports that there are orphan changes to the database that the first instance is connected to, even before the second instance connects to any database. Closing the first instance's connection and reopening it solves the error.
[26 Jun 2012 19:33] Michael Doube
Bug present on Ubuntu 11.04, MySQL Workbench v5.2.40 rev 8790 64-bit.

Query followed this syntax, with own variable and table names:

SELECT DISTINCT store_type FROM stores
  WHERE EXISTS (SELECT * FROM cities_stores
                WHERE cities_stores.store_type = stores.store_type);

http://dev.mysql.com/doc/refman/5.0/en/exists-and-not-exists-subqueries.html

MySQL server '5.1.63-0ubuntu0.11.04.1'
[16 Mar 2014 12:14] Arnaud Adant
Impacts 6.0.9 on MacOS. 
No idea on how to repeat. It just happens after a query is successfully executed. The following queries all fail with the error "No such table: changes"
Maybe a code review could help.
[16 Apr 2014 14:59] István Tóth
Just happened to me with mysql-workbench-community-6.1.3-1.fc20.x86_64.rpm

The tab with query was open for about 6 hours, when I tried to repeat the query, and I restored the database under it before I run the wery again.

A restart helps.
[3 Jun 2014 17:34] Nilo Teixeira
Same thing happening here on Mavericks, Workbench 6.0.7

Workbench was left opened for a day or something, and when I returned all queries issue that error message.

A restart is a valid workaround.

Thank you.
[11 Mar 2015 21:57] Paul Coene
Still happens on 14.04.  Also when you rearrange tabls - and reexecute commands it seems to try to execute the wrong commands.  It seems to happen more often in these cases.
[6 Jul 2015 17:17] Greg Havener
Still occurring with Mysql Workbench 6.1 on OS X Yosemite 10.10.3.  If Mysql Workbench is left open and the computer is put to sleep, when the computer wakes again Workbench does all kinds of odd things.  Sometimes is works OK, sometimes it will just disable the Execute tool but not actually run a query (requiring a restart of Workbench), sometimes it will start displaying the error "No such table: Changes" on every query (requiring a restart of Workbench), sometimes it will display an error like "Lost connection" on every query (again requiring a restart of Workbench). 

It seems to me that the application does not recover well from losing connections, in combination with time passing while the computer is sleeping.
[21 Dec 2015 20:08] John Moses
Happened to me on Mac OSX 10.8.5 on Mysql Workbench 5.2.45
[5 Apr 2016 6:36] Pablo Typ
Happens for me:
Workbench: 6.0.8.11354 build 833
Linux: 14.04.2 LTS, Trusty Tahr

It seems to have happened after using x2go to this machine and in there starting a new workbench on a new session while workbench was still running in old session.
I also modified a file that the old sessions workbench was using.