|With nearly 400 connections, this is absolutely mandatory !!||10||23-APR-15|
|Can you explain what you mean by "Folders in the navigator are currently not persisted"? Please consider some of the less complicated request about the folders in the vote comments. Like the request for subfolders. These smaller requests will do a lot to maake SQL Developer more user friendly and improve organization of the tool.||10||29-SEP-14|
|Allowing sub folders in the connection hierarchy (at least) would make my experience with SQL developer much better. We have multiple databases hosted by the same machine and each database needs at least two connections one for administrator role and the other for normal connection. Given that we have a lot of Oracle machines, the administration of connections gets messy very quickly.||10||29-JUN-14|
|Folder structure with only one folder level is simply not sufficient when having to deal with lots of database connections (currently about 50 connections in my setup). Subfolders in combination with the above request (persisting folder navigation) would make SQL Developer a MUCH better tool.||10||22-APR-14|
|Folder structure with only one folder level is simply not sufficient when having to deal with lots of database connections (currently about 200 connections in my setup). Subfolders in combination with the above request (persisting folder navigation) would make SQL Developer a MUCH better tool.||10||06-MAR-14|
|Would be very useful||10||05-FEB-14|
|Suggestion: Add an Option to limit un foldered connection lists (example: top right) to only currently open / active connections.
|The folder are useful for us.||10||17-OCT-11|
|Much needed. At the very least, please give us a way to filter/search the connections: display only those connection for which name OR host OR port OR user contain a given search string.||10||30-SEP-11|
|folders have been implemented in a strange way why not have a heiarchical model like explorer? or the unix filesystem? where you can have sub directorys as well. even oracle has a self join concept to allow heirarchies. the implementation of folders as has been done (flat namespace, not included in xml export) is akin to asking someone to design a filesystem for an OS that can have subdirectories why on earth would you bother... the question has been answered fully before and there is code in the standard java library for this. Can anyone invent me a thing to help roll things along... fewer corners the better?||10||27-MAR-11|
|would like to have it||10||04-NOV-10|
|This would be a great help to me. I already have to keep my database list trimmed to keep too many entries out of the new SQL worksheet drop down, and scrolling around in a worksheet or report's connection selector is a big annoyance.||7||17-MAY-10|
|While you are at it, more then just one level of folders would be nice as well:
You get the idea.
And once the folders are persisted, I suppose they can be exported also, along with the connections.||0||01-APR-09|
|An additional consideration is the ability to add an optional filter to the display lists, so that only the contents of user specified folders (one or more0 show up in the list.
For example, when working disconnected at home, I simply do not want to see the list of connections for the database at work. Ditto if I have different sets of client connections in their own folders.||5||30-SEP-08|
|seems logical to implement this||10||11-JUN-08|
|Needed to make the folders useful||10||14-APR-08|