You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: