Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Is it possible to store database connections just for current workspace?
Is it possible to store database connections just for current workspace? It would be nice being able to store connection settings as part of the workspace and git repository.
Comments
-
No it is not possible in the current release...
Can you tell me more about the workflow that would make this helpful to you? Do you have tons of databases, each for each workspace? Are you trying to make it easier for other developers who share a workspace with you? Please describe what you want to do in more detail.
-
We usually have one connection for every schema for every instance, so we can choose who can access to at any given time. The idea is having the connection info included within the git repository so we would be able to share that config between developers, and for keeping things more organized. If I'm working in a workspace of a given instance, I don't really need to see tons of connections of other instances.
-
Thanks, this is very interesting. I will discuss with the team.
-
Yes. I work on many projects and having a stupid long list of database connections isn't very practical. It would be nice that when I open a specific workspace or folder that I have just the connections relevant to that project listed.
In fact, the easiest might be to add a `oracle.bookmarks` key to the .vscode/settings.json file that would just have the names of the connections "bookmarked" for this project. Then in the Oracle Explorer pane, pull the bookmarked connections up into a "Bookmarked" list that is expanded above the current "DATABASE" list of all my connections. That would allow:
- DB connections are still configured at a single place where my password may be
- The project can specify which connections are relevant to highlight in the Oracle Explorer pane
- When I go to Oracle Explorer, I have the best of both worlds (current project connections and all my connections)
- Bonus: also add a oracle.connections key to .vscode/settings.json that you could commit the connection info so a new developer gets a template for the connections (no password stored here, they need to create/setup the connection themselves into the current place)
-
Thanks again for both of your feedback. We are trying to add a feature like this (unclear when it will make it into the product).
I may ask you for more feedback in the coming weeks.
