Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Usability] Double-click on database to set active (PostgreSQL, maybe others?)
See original GitHub issuePostgreSQL only allows a connection to access one database at the time.
So when you double-click a database other than the active one, or try to expand its Schemas folder, this will always result in this error message:
And you always need to click OK, right-click the database, and choose Set active before proceeding.
It would be nice to skip this extra step, and just make it so that when you double-click a PostgreSQL database it gets automatically set as active. It’s a deliberate action and hard to do by accident.
It may make sense to make this the default behaviour for other databases as well, for consistency, but I’m less sure about that.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This feature (auto-switch by double-click) had disappeared since 5.2.0. I wish it is brought back. Without it, I sometimes query/update a wrong database - rather dangerous.
Please bring this feature back.