Re: createdb.exe and psql.exe without Promting Password
От | Raymond O'Donnell |
---|---|
Тема | Re: createdb.exe and psql.exe without Promting Password |
Дата | |
Msg-id | 4991FEF4.1060105@iol.ie обсуждение исходный текст |
Ответ на | Re: createdb.exe and psql.exe without Promting Password (Sam Mason <sam@samason.me.uk>) |
Ответы |
Re: createdb.exe and psql.exe without Promting Password
|
Список | pgsql-general |
On 10/02/2009 21:47, Sam Mason wrote: > On Tue, Feb 10, 2009 at 07:22:24PM +0100, IIIigo Barandiaran wrote: >> What does "visible to the script" means? > > Each command interpreter has its own set of variables; you need to set > them in the correct one. For example, starting one copy of "cmd" and > typing "SET var=value" and then closing it and starting another one and > running your "script" won't work because they are different interpreters > (i.e. different instances, or processes, of the same executable, or > program). > > If you're executing "SET ..." in one command interpreter and then double > clicking on your script (a .bat file?) then you're effectively starting > another interpreter on that one script, it will exit when it's reached > the end of your script. I couldn't have put it better! :-) You could create a system-wide environment variable via right-clicking on My Computer, selecting properties, then clicking "Environment variables" - but this is a *really* bad idea for storing a password, as it's visible to anyone using the computer. Far better to use the .pgpass file. Ray. ------------------------------------------------------------------ Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland rod@iol.ie Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals ------------------------------------------------------------------
В списке pgsql-general по дате отправления: