Completion from multiple databases about vim-dadbod-completion HOT 4 CLOSED

It seems like there are three options: pulling in completions from all databases on a server, keeping multiple database connections to pull completions from, or switching the current database for the buffer.

The first one I think is obviously a bad idea.

The other two I think probably belong best in dadbod-ui (or maybe another small plugin that would support both dadbod and dodbod-ui?). Creating a function to switch the connection for the current buffer would probably be simple to implement though it would still require manual switching, which isn't perfect. Something like a workspace feature that could send vim-dadbod-completion multiple database connections to complete from should make completing from multiple databases seamless, but would require a good deal more work from both plugins.

from vim-dadbod-completion.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from vim-dadbod-completion.

Sounds like this issue is best solved over at dadbod-ui.

from vim-dadbod-completion.

Dadbod-ui already allows for multiple active connections. I think to get multiple database completion working the changes need to be made here.

• If not using dadbod-ui, no changes.
• If using dadbod-ui get all active database connections for the same server that the current buffer is connected to
• Add database key to the cache
• Query each active database connection and for each add all schemas/tables/columns etc. to the cache

Am I missing anything big?

from vim-dadbod-completion.