If MySQL Workbench CE loses its connection to a server (e.g. when my laptop goes to sleep), it opens a login window for that server. I cannot then close Workbench without logging in to the server again, even if I do not need to run any further queries there. If I close the login window it reopens again before I have chance to close Workbench. I keep the server passwords in a password keeper, so I have to log into two systems unnecessarily.
Is there a way to close Workbench without logging in to the server again?
I am on version 6.3, but I think the behaviour is common to others.
Related
What is the quickest way to open a command-line interface to a Google Cloud SQL database?
I like the old-school mysql command line interface, so currently I open a terminal from the cloud console and then connect with gcloud sql connect .... This then shows a message "Allowlisting your IP for incoming connection for 5 minutes.." which then sits for well over than a minute before the password prompt is given.
Compounding things, the cloud console disconnects if you leave the tab for 10 minutes so you have to do it all over again.
Are there any options to more quickly open a mysql command line client for quick queries? Should I spin up a linux server and connect from there? Load a MySQL client on my PC and connect from there? All of those are extra steps that I have to figure out, so I was wondering which connection method will give me the quickest connection speed just for simple querying.
Use Cloud SQL Auth Proxy with a local database client, but just keep the proxy running
I just installed mysql workbench 6.3.6 on ubuntu 16.04.
When I connect to db, many icons on the top are disabled ( grayed ) and doesn't show any default schemas (such as sys and etc ) on the left
as you see in the figure, so I cannot create db and tables in workbench.
I followed this youtube video, https://www.youtube.com/watch?v=u6p2OU491Ss
and many icons are activated ( not grayed in the video ) in workbench.
I created mytest db manually in command line and icons in both local instance and mytest are grayed in workbench. But I can connect to mysql in command line with username root and password that I reset.
This is because Test connection failed in workbench. don't know why.
FYI, when I reset root password, I used this command:
UPDATE mysql.user SET authentication_string=PASSWORD('newpassword'), plugin='mysql_native_password' WHERE User='root' AND Host='%';
You have no valid connection, that's why the buttons are disabled (and hence shown in gray). Open MySQL Workbench with valid credentials and everything should start working as you expect. The connection test error seems to indicate that your MySQL server is not running.
I use SQL workbench to connect postgresql. But I frequently get following error
This connection has been closed.
when ever I kept the window idle for 2-3 minutes.
I am not sure where to the change the settings. Please help me .
Version : Build 118.7
If the server is configured to disconnect idle connections, you can configure a statement that is sent to the database server in regular intervals.
This is done in the connection profile. Click on the "Connect scripts" button:
Connection dialog
Then enter a statement for "Statement to keep connection alive".
Connect scripts
In the "Idle time" you can configure how often the statement should be executed. "1m" means that it's run every minute unless you run statements manually (or do something in the DbExplorer)
This should prevent the server to disconnect your session.
I have a lot of tabs and queries open in MySQL workbench. I left it open before I went to sleep, but this morning I am getting an error MySQL server has gone away when trying to run queries.
The database is up, and I am able to connect to it if I open a new connection on MySQL workbench, but the current connection is dead. How do I reconnect?
I don't want to open a new connection as I would have to copy my queries and tabs over.
Done it.
Query Menu -> Reconnect to Server
I want to increase PostgreSQL's Studio login/session time out time. When I leave PostgreSQL Studio to idle just for some time, I get the following message:
You have been logged out due to inactivity. Please relogin or exit.
I am using PostgreSQL from BigSQL 5.0.3 package bundle. Actually, I am researching about compability of MS SQL Server and PostgreSQL queries.
As I am using Postgres now for learning purpose rather than security, I feel it annoying to login frequently.
How can I increase the login/session timeout inside PostgreSQL Studio?
Postgres itself doesn't have an idle connection timeout. This is coming from something else.
Unfortunately, the timeout value is hard-coded to 30 minutes in PostgreSQL Studio. You should only see that if you are not using Studio at all for 30 minutes. Its a pretty simple matter to move that property to the config file so it can be changed. We just need to write a patch.
The timeout is to prevent Studio from holding open idle connections to PostgreSQL. PostgreSQL Studio uses connection pooling to manage connections back to the database so if the browser connection goes away without logging out, we need a way to remove those connections.