Bug #13521 | SQL statements are being erased on tab change | ||
---|---|---|---|
Submitted: | 27 Sep 2005 11:49 | Modified: | 29 Sep 2005 14:35 |
Reporter: | Diogo Domanski | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.1.15 | OS: | Windows (Windows XP) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[27 Sep 2005 11:49]
Diogo Domanski
[27 Sep 2005 13:09]
Oliver Peters
the same here and it doesn't matter if the query is executed or not
[28 Sep 2005 18:58]
B. Campbell
Erasure includes any SQL statement - whether typed in, opened query file, or query browser generated (e.g. table double click for simple select). To Replicate: Click on any other open tab (or open a new one) then back to the previous tab -- 'poof' SQL statements are erased. OS: Windows XP, SP2
[29 Sep 2005 14:35]
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 bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html
[10 Oct 2005 13:27]
David Seaton
Work around.. Not sure if it always works, but using the Back and Forth buttons sometimes will restore your sql. You may have to use execute first, can't remember. But doing that has saved me a couple of times.