Session Isolation: Why One Top Tab Binds One Database
In legacy database tools, a massive sidebar tree exposes dozens of connections and thousands of tables simultaneously. Query tabs are loosely coupled to schemas—making it alarmingly easy to run a destructive query meant for staging against a production database.
VloamDb enforces strict Session Isolation: every top-level tab binds directly to a specific "Connection + Database" tuple with its own lifecycle. Table browsing, search scopes, and query execution are strictly sandboxed within that database.
Open Production, Staging, and Local database tabs simultaneously. Each tab maintains its isolated context, colors, and query history without cross-contamination.
Tab Context Actions & Bulk Closing Policies
During deep debugging sessions, you often open dozens of related tables in quick succession. Closing them individually slows down productivity.
VloamDb provides IDE-grade tab management across top-level database tabs, inner table tabs, and query consoles:
| Action | Trigger | Description |
|---|---|---|
| Close Tab | ⌘W / Ctrl+W 或右键菜单 | Closes active table, script, or result tab. |
| Close Others | Right-click tab | Keeps only the selected tab, dismissing all background clutter. |
| Close to the Right | Right-click tab | Closes all tabs positioned to the right. |
| Close to the Left | Right-click tab | Closes all tabs positioned to the left. |
| Close All | Right-click tab | Resets the workspace by closing all open tabs. |
Open Tabs Drawer & Environment Color Cues
In addition to the horizontal tab strip, VloamDb features an "Open Tabs" drawer at the top of the sidebar:
- Vertical Tab Overview:When horizontal tabs overflow the screen, the sidebar drawer displays a clean vertical list.
- Instant Tab Filtering:Quickly search across active tabs without switching back and forth.
- Cross-UI Color Tagging:Assigned connection colors (Red for Prod, Yellow for Staging, Green/Blue for Local) consistently render across tab borders and sidebar indicators.