Skip to content

Conversation

@psteinroe
Copy link
Collaborator

@psteinroe psteinroe commented Oct 26, 2025

adds connectionString to the database config. if provided, it is preferred over the individual host, port, etc. settings.

note that the ConnectionKey still checks only based on the basic infos. This could potentially lead to an issue if the same workspace instance accepts multiple connections to the same database. if one is e.g. adding different sslmode settings via the connection sring, it would be re-used even if another just has the same host + port + user + database. I do not think we need to distinguish here since that case should not really happen unless you host this as a service that is shared among many people.

fixes #575

Copy link
Collaborator

@juleswritescode juleswritescode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

love it, maybe this is a good opportunity to also finish #302 ?

@psteinroe
Copy link
Collaborator Author

love it, maybe this is a good opportunity to also finish #302 ?

yeah, it could be as simple as adding a ENV to the cli option

# Conflicts:
#	crates/pgt_cli/tests/commands/check.rs
@psteinroe psteinroe merged commit 02af023 into main Oct 28, 2025
8 checks passed
@juleswritescode juleswritescode deleted the feat/more-connection-options branch October 28, 2025 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

allow connecting via connectionString

3 participants