MySQL Workbench – Closed Queries Re-open When Connecting to DB

mysql-workbench

Using MySQL Workbench latest version (6.3) I've set up an Amazon EC2 connection successfully. Every time I open the connection, I've noticed all queries I did before are being opened, even if I closed them using right click -> "Close All" option. These queries have dynamic names like {0303FFF4-FB6D-4EF3-A9EC-2...

I don't want these queries to remain stored, as most of the time they're just temporary queries I need for some quick data gathering.

Can somebody please help me with these? What do I need to do?

Best Answer

I thought this was some kind of auto-save feature from Amazon EC2 instance or some kind of bug, but nope my bad. I found bug report and at the bottom of the page this is the answer:

Andres Giordano: This is not a bug!!! You have to go to Edit --> Preferences --> General --> SQL Editor (panel) and uncheck "Save snapshot of open editor...."

That's the correct answer. Once this option is disabled, no more queries are stored and re open. I hope this tip is useful for somebody. Greetings!

Related Solutions

Mysql – Incremental backups using MySQL Workbench

To be frank, if you are using a GUI tool as your backup strategy, you are doing it wrong. Backups need to be scripted, automated, and regularly tested or else you might as well not have them. If your database is very small (a few gigabytes), there is no point in doing incremental backups: backup the entire database with mysqldump and use binary logs in statement format for point in time recovery, or using a slave, shut down the slave an archive the binary files (cold backup).

If you are using InnoDB and really need incrementals, there is Xtrabackup from Percona or innodbhotbackup.

Xtrabackup is a great tool which I highly recommend. It will perform true incremental backups with minimal impact to the server.

Mysql – –local-infile=1 using MySQL Workbench

According to the MySQL Documentation on LOAD DATA INFILE

For security reasons, when reading text files located on the server, the files must either reside in the database directory or be readable by all. Also, to use LOAD DATA INFILE on server files, you must have the FILE privilege. See Section 6.2.1, “Privileges Provided by MySQL”. For non-LOCAL load operations, if the secure_file_priv system variable is set to a nonempty directory name, the file to be loaded must be located in that directory.

As long as you have FILE privilege, you can do this in SQL Editor

SET GLOBAL local_infile = 1;

Best Answer

Related Solutions

Mysql – Incremental backups using MySQL Workbench

Mysql – –local-infile=1 using MySQL Workbench

Related Question