Wednesday, May 2, 2018

Re: dbext: unable to connect to MySQL database

On Wednesday, May 2, 2018 at 12:06:43 PM UTC-7, David Fishburn wrote:
> Thanks very much for responding. Yep, all on the same machine, and I see the exact same behavior regardless of whether I am attempting to query my localhost or a remote server.
>
>
>
> No problems outside of Vim: queries work fine via CLI or a client such as MySQL Workbench.
>
>
>
>
>
>
>
>
>
>
> > Can you supply a mysql command line call that correctly connects to the database.  
>
>
>
> You did not provide this information, just omit the password.
>
>
> David

Hi David,

Sure.

Here are a couple of different CLI approaches, both on localhost. Both of these return the expected result.

mysql -h localhost -u myusername -p
select * from lter10_arthropods_production.sites;

mysql -h localhost -u myusername -p -D lter10_arthropods_production
select * from sites;

I have a similar config in my vimrc for for the MySQL localhost, here trying naming the database explicitly and not doing so. Also tried with and without passing a password.

let g:dbext_default_profile_mysql_local = 'type=MYSQL:host=localhost:port=3306:user=myusername'

let g:dbext_default_profile_mysql_local_arthropods = 'type=MYSQL:host=localhost:port=3306:user=myusername:dbname=lter10_arthropods_production'

With either connection setting, running the above query with or without identifying the database name, I get the same result: man page details of MySQL, connection settings, and the query. I have attached a truncated version.


Thanks for your help.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment