On Sep 29, 11:10 pm, David Fishburn <[email protected]> wrote:
> >> Probably, that's just a minor bug in a function "DB_PGSQL_execSql" - it
> >> constructs command to be executed as
>
> ...
>
> > Hi Mikalai, thanks for your answer. Your tip was very useful to point
> > me in a good direction.
> > Turns out there is no easy way to pass a password as a command line
> > parameter to psql. You can use -W switch to make psql ask for it but
> > you will have to type it as a second step. I finally created a
> > ~/.pgpass file as suggested here [1] and now dbext is not asking the
> > pass anymore.
>
> Correct. PGSQL does not allow passwords to be set from the command
> line which is the reason dbext does not provide it.
>
> > What's funny is that this started happening yesterday
> > with a fresh pgsql database. I can recall at least three other pgsql
> > databases I had queried with dbext and none of them prompted for the
> > password. Don't know why.
>
> Mariano, I can only image someone had already set those settings in
> the database you were connecting to.
>
Sounds plausible
> > [1]http://www.postgresql.org/docs/current/interactive/libpq-pgpass.html
>
> As you have pointed out, that is the only way to control access to the
> database.
>
> I am glad you are connecting and running again.
>
Thanks for confirming it was the best solution. And thank you very
much for such a fine plugin.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
