Connection folders
Group servers into nested folders in the Database Explorer.
The Database Explorer supports user-defined folders for organizing your connection list. Folders can be nested to any depth and are persisted per-machine, encrypted alongside your other QueryDen state.
Switching view modes and creating folders
Click the folder icon in the top-right of the sidebar header. A popover opens with the three view modes and a + New folder action:
- Folders (default) — your own hierarchy. With no folders defined, this renders identically to Flat — the popover is just always the same place to come back to.
- By type — auto-grouped by database engine (Postgres / MySQL / SQLite / etc.).
- Flat — connections in the order you created them.
The currently active mode is shown as a filled radio dot. Pick a different mode and the popover closes immediately.
The + New folder action lives in the popover regardless of which mode you’re currently in — picking it prompts for a folder name and switches you to Folders view so you can see what you just created.
View-mode choice is not persisted across launches in v1; every app start defaults to Folders. To create a subfolder of an existing folder, right-click it and pick New subfolder.
Moving connections and folders by dragging
You can drag and drop connections and folders to reorganize the tree:
- Connections — drag a connection row onto a folder to move it inside that folder, or onto the empty area at the bottom of the tree to move it back to root.
- Folders — drag a folder onto another folder (or root) to reparent it.
Valid drop targets are highlighted with a dashed border when you hover over them. Dropping a folder onto itself or one of its descendants is blocked automatically (cycle detection).
You can also use the right-click menu’s Move to folder… option for any connection or folder — the picker shows your full folder tree and is also keyboard-accessible.
Reorganizing folders
Right-click a folder for the full set of actions:
- Rename — change the display name.
- New subfolder — add a child folder.
- Move to folder… — reparent (including back to root). QueryDen rejects any move that would form a cycle (a folder being its own ancestor).
- Delete folder — remove the folder. Connections and subfolders inside it are reparented to the deleted folder’s parent, not deleted. So deleting
Production/EUwith two connections inside leaves those two connections directly underProduction.
The cascade-reparent behavior means you can’t accidentally lose connections by deleting a folder. The connections are unaffected.
Where is this stored?
Folders are saved to folders.json in the QueryDen app data directory (e.g. ~/.local/share/com.queryden.app/ on Linux, equivalent per OS). The file is encrypted with the machine-bound key — the same scheme that protects connections.json and query-history.json. Copying the file to another machine won’t reveal your folder tree.
Folder membership for each connection is stored as a folder_id field inside connections.json. Older connections.json files without that field load cleanly (the missing field is treated as “no folder”).