| From: | BladeOfLight16 <bladeoflight16(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SQL Path in psql |
| Date: | 2013-09-09 04:10:00 |
| Message-ID: | CA+=1U=UXOSzoA7qTmvMYnj=CiscNsJ34b3oaE958OTBM2qERHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 6, 2013 at 1:58 PM, David Kerr <dmk(at)mr-paradox(dot)net> wrote:
> I suspect this feature makes more sense on a windows platform. On linux
> where we can
> go psql -f ${SQLPATH}/file.sql . it becomes less pressing. Even Oracle
> on unix/linux where you can go sqlplus <<EOD @${SQLPATH}/file.sql EOD.
> makes
> it less a requirement.
>
I don't see why you couldn't do the same thing in command prompt on Windows:
SET PGSQLPATH=C:\somedir
psql -f %PGSQLPATH%\file.sql
Naturally, you could configure a permanent environment variable instead of
using SET.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jayadevan M | 2013-09-09 04:12:38 | Re: [pgeu-general] Call for design: PostgreSQL mugs |
| Previous Message | Rob Sargentg | 2013-09-09 02:27:50 | Re: Sum of columns |