How do I set the mysql workbench preferences permanently forever - mysql-workbench

I set the SQL editor DBMS connection read timeout interval to 0 so many times that there just has to be a way to save it so its the default option when I open MySQL Workbench.

Related

How to change max_connections for Postgres through SQL command

We have a hosted PostgreSQL, with no access to the system or *.conf files.
I do have a admin access and can connect to it using Oracle SQL developer.
Can I run any command to increase the max_connections. All other parameters seems to be ok shared mem and buffers can hold more connections so there is not problem there.
Changing max_connection parameter needs a Postgres restart
Commands
Check max_connection just to keep current value in mind
SHOW max_connections;
Change max_connection value
ALTER SYSTEM SET max_connections TO '500';
Restart PostgreSQL server
Apparently, the hosted Postgres we are using does not provide this option. (compose.io)
So the work around is to use a pgbouncer to manage you connections better.

MySQL Workbench: Reconnecting to database when "MySQL server has gone away"?

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

Can I set a default schema for a connection in Oracle sql developer 4?

Is there a way to set the default schema for a Database connection in Oracle SQL Developer version 4+? I see this link for previous versions:
http://www.javaforge.com/project/schemasel
...but I can't figure it out for Oracle SQL Developer version 4.
The way to do this at the tool level would be to run a session startup script.
Create a text file 'logon.sql' with the script "alter session set current_schema = yourschema;"
Save it anywhere - I recommend saving it somewhere in your database install location.
In SQL Developer go to Tools -> Preferences -> Database
Check the box for "Run connection startup script on each new database connection"
Browse and select the above file.
That should make you default to that schema every time you login.

How to change PostgreSQL Studio's inactivity timeout?

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.

How to set connection timeout value for pgAdmin?

I am using pgAdmin to connect remotely to my database as phpPgAdmin is a bit limited in its features. Only problem is if I leave the SQL window open without running a query for a few minutes, then it says I need to reconnect.
Is this a setting I need to change in my database to keep remote connections alive for longer or is it a pgAdmin setting?
It is client setting.
You need specify connect_timeout in your config file.
29.1. Database Connection Control Functions
29.14. The Connection Service File