| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Loading a list of SQL scripts with relative paths |
| Date: | 2005-05-10 16:29:58 |
| Message-ID: | 200505101829.58576.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Michael Glaesemann wrote:
> This works well, but I think I'll have to change all of the paths
> when I move the group of scripts to the production server to load
> them. What I'd like to do is be able to use paths relative to the
> file that contains the \i commands. This doesn't seem to work when
> using \i.
The paths are, as you probably found out, relative to the current
working directory. Since the path of the current script is not exposed
as a variable or something like that in psql, I don't think you can do
any computations within psql to achieve what you want. Others may have
ideas how you can organize your scripts differently, though.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-10 16:36:47 | Re: pg_dump fails on 7.4 Postgres |
| Previous Message | Jim C. Nasby | 2005-05-10 16:11:22 | Re: Trigger that spawns forked process |