Separate connections per project (like DataGrip projects)

Ouverte
#4,307 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@datlechin y travaille déjà.

Depuis le 20/11/2026.

  • #4376 par @datlechin — ouverte

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
swift
Domaine
databases, desktop

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Swift
Étoiles
6.2k
Forks
412
Merge moyen
7 h 38 min
PR mergées (30 j)
536

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TableProApp/TablePro

Toutes les issues de TableProApp/TablePro

Issues similaires

Plus d'issues Swift

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.