Re: createdb.exe and psql.exe without Promting Password - Mailing list pgsql-general

From Sam Mason
Subject Re: createdb.exe and psql.exe without Promting Password
Date
Msg-id 20090210214746.GZ3008@frubble.xen.chris-lamb.co.uk
Whole thread Raw
In response to Re: createdb.exe and psql.exe without Promting Password  (Iñigo Barandiaran <ibarandiaran@vicomtech.org>)
Responses Re: createdb.exe and psql.exe without Promting Password
List pgsql-general
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.

--
  Sam  http://samason.me.uk/

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Referencing Cursor/Row/Record Fields in PL/PgSQL
Next
From: Max Strömberg
Date:
Subject: In need of help with message fetching query