MySQL Bugs: #53376: Change in query requires two executions for change to be reflected.

Bug #53376	Change in query requires two executions for change to be reflected.
Submitted:	3 May 2010 14:35	Modified:	6 May 2010 16:37
Reporter:	Daniel Katz	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.20	OS:	Windows (7)
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any
Tags:	execute statement, sticky query

Description:
Something is making the last query "sticky" so that when you make a change to the active query and hit 'execute current query' (ctrl-enter), the _previous_ version of the query will be executed.  Then if you run it again, it will run the current version of the query.

I think it's always one step behind.

How to repeat:
Run a few queries, then edit a query and try to run it.  Notice that it's not the latest version?

Suggested fix:
no suggestion.

Thank you for the bug report.

Failed to repeat. This bug was fixed before 5.2.20 release.
Could you recheck the version? Or maybe there are any special actions required to reproduce it?

I as well can't reproduce this today although I'll keep trying.

I can say that I'm using 5.2.20 rev 5783, so the problem might still be lurking around.   It's just not easily reproducible.