Feature Request
Allow “Open in TablePlus” to use a specific database and user.
Description
The “Open in TablePlus” action (in the dropdown menu next to the start/stop button for each server) always opens a connection using default values.
This affects all supported database types, where TablePlus falls back to its own defaults instead of a project-specific database/user.
Problem
- Connection may fail if default database/user does not exist (my case)
- Requires manual "Edit" in TablePlus every time
- Breaks the expected one-click workflow
Expected Behavior
Allow configuring connection details per server, such as:
- Default database
- Default user
Alternatively, allow linking to an existing TablePlus connection.
i.e (PostgreSQL)
For example, instead of always opening with:
- user:
postgres
- database:
postgres
Allow opening with something like:
- user:
username
- database:
db_name
Thanks :)

Feature Request
Allow “Open in TablePlus” to use a specific database and user.
Description
The “Open in TablePlus” action (in the dropdown menu next to the start/stop button for each server) always opens a connection using default values.
This affects all supported database types, where TablePlus falls back to its own defaults instead of a project-specific database/user.
Problem
Expected Behavior
Allow configuring connection details per server, such as:
Alternatively, allow linking to an existing TablePlus connection.
i.e (PostgreSQL)
For example, instead of always opening with:
postgrespostgresAllow opening with something like:
usernamedb_nameThanks :)