Separate connections per project (like DataGrip projects)

未關閉
#4,307 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@datlechin 已經在處理了。

開始於 2026年11月20日。

  • #4376 來自 @datlechin —— 未關閉

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
swift
領域
databases, desktop

研究方向

Start by reading the related workspace issues #2088 and #2217 and tracing how connections, search, Recent, saved queries, and history are stored and filtered. The issue proposes project profiles that isolate all of these, with a default profile, or a group-only filter that also affects search and Recent. Done means project data stays separated across the listed views and the default profile preserves existing behavior.

由索引模型根據 Issue 內容生成。

描述

enhancement
Problem

At work I'm on several projects at the same time, and each one has its own set of databases (dev, staging, prod). In DataGrip I keep one project per product, so when I'm working on project A I only see project A's data sources and consoles.

In TablePro it's all one list. I use groups and colors, which helps, but search and Recent still show everything, and I've come close to opening another project's prod DB by mistake more than once. Saved queries and history seem to be shared too, so they get mixed up pretty quickly.

To be clear, I don't mean "workspace" like in #2088 / #2217. I mean a way to keep one project's stuff apart from another's.

Proposed solution

Something like projects or profiles: pick one, and the connection list, search, Recent, saved queries and history only show what belongs to it. Keep a default one with everything so nothing changes for people who don't care about this.

If that's too big, even a "show only this group" toggle that also applies to search and Recent would solve most of it for me.

Alternatives considered

Groups + tag filter is what I do now. It's fine for organizing but it's just a filter, I still have to remember to set it, and it doesn't touch saved queries or history.

A separate macOS user per project would work, but that's way too much hassle.

Platform

macOS

Related database type

N/A / General

主要語言
Swift
星號
6.2k
分支
412
平均合併
7 小時 38 分鐘
30 天內合併 PR
536

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TableProApp/TablePro 的其他 Issue

查看 TableProApp/TablePro 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。