Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Steps to reproduce this issue
Current query host/connection information is not prominent
User interface could possible highlight current query target ( localhost / aws in my example).
In query tab before query name (query 1). display also connection name, so it's easy to spot where a query is executed.
Last version, 10.2.0.5730
Having the session name in each query tab would make the user think these tabs are bound to that session, which is not true. As soon as you navigate to another session, any query fired in any tab runs on that selected session.
What if the tree on the left would gray out unselected sessions even more than they are now?
Totally missed that, my bad. I must be more cautious on this, good to know!
Add an option for users to activate a "only one connection at time", so it's more hard to mess things up