Separate connections per project (like DataGrip projects)

Abierto
#4,307 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@datlechin ya está trabajando en esto.

Desde el 20/11/2026.

  • #4376 de @datlechin — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
swift

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Swift
Estrellas
6.2k
Forks
412
Merge medio
7 h 38 min
PR fusionados (30 d)
536

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TableProApp/TablePro

Todos los issues de TableProApp/TablePro

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.