Skip to content

[Feature Request] Support For Multiple DB URLs #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
amokan opened this issue Dec 12, 2024 · 0 comments
Open

[Feature Request] Support For Multiple DB URLs #3

amokan opened this issue Dec 12, 2024 · 0 comments

Comments

@amokan
Copy link

amokan commented Dec 12, 2024

Love the extension! Super helpful.

I have a project where there are two different Postgres instances (for various data partitioning reasons). So that translates to a pair of development databases running locally in my Postgres.app. I get by just configuring the most commonly used db of the two for this extension, but it would be great to have the ability to handle both.

I'm sure my scenario is somewhat edge-case~ish, but just wanted to raise the situation for future consideration or a potential PR contribution.

Regarding a PR, I think my question would be around any potential 'prior art' for similar scenarios in the Zed ecosystem. My thinking is if the extension supported multiple databases, the first pass would just be a case where all configured databases would have their schema pulled to provide the table list via /pg-schema <table name>. A more sophisticated implementation could later support something like /pg-schema <database> <table name> 🤷‍♂️ .

Would love your thoughts when time permits.

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

No branches or pull requests

1 participant