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 been trying to use Dadbod to connect to the sql server, I could connect to it by using DBext without issues, but when I tried to use dadbod with the following parameters
It just gives me the following errors:
I have been researching for quite a while, I just couldn't work out why. The researching told me that it's something to do with the quotes or passing the connection string issue. Can you please advise?
I have also tried to integrate it with vim-dadbod-ui by having this line in my init.vim (using neovim).
When I tried to open the database in the UI, it gives me the same error from dadbod-ui:
Regards
Gernacke
The text was updated successfully, but these errors were encountered:
Dear Tpope,
I have been trying to use Dadbod to connect to the sql server, I could connect to it by using DBext without issues, but when I tried to use dadbod with the following parameters
![dadbod](https://user-images.githubusercontent.com/43158395/79526225-244b5800-80a8-11ea-895f-30d07f3109f0.JPG)
![sqlcmd error](https://user-images.githubusercontent.com/43158395/79526278-42b15380-80a8-11ea-9e96-3cd7c20369ad.JPG)
![dadbod-ui](https://user-images.githubusercontent.com/43158395/79526640-15b17080-80a9-11ea-8514-bc1d5bfbf69d.JPG)
![dadbod-ui-error](https://user-images.githubusercontent.com/43158395/79526678-282baa00-80a9-11ea-82e6-64773439831b.JPG)
It just gives me the following errors:
I have been researching for quite a while, I just couldn't work out why. The researching told me that it's something to do with the quotes or passing the connection string issue. Can you please advise?
I have also tried to integrate it with vim-dadbod-ui by having this line in my init.vim (using neovim).
When I tried to open the database in the UI, it gives me the same error from dadbod-ui:
Regards
Gernacke
The text was updated successfully, but these errors were encountered: