-
Notifications
You must be signed in to change notification settings - Fork 20
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
Completion from multiple databases #34
Comments
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. |
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. |
Sounds like this issue is best solved over at dadbod-ui. |
Dadbod-ui already allows for multiple active connections. I think to get multiple database completion working the changes need to be made here.
Am I missing anything big? |
I am unsure if this is a feature request, or a need for better understanding on my part... Thus far, I only get completion of table names and columns from the database specified in the connection. But when I
SELECT FROM OtherDatabase.dbo.OtherTable
I do not see completion suggestions.Is this by design, or am I doing something wrong?
I am using a sqlserver connection.
If this is by design, might you consider adding this feature? Or perhaps this would be a feature added to vim-dadbod?
The text was updated successfully, but these errors were encountered: