From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Harald Fuchs" <hf1110x(at)protecting(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql substitution variables |
Date: | 2007-01-24 01:17:39 |
Message-ID: | b42b73150701231717t1c8dcf02td32b5135c1e37ba2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 24 Jan 2007 00:21:44 +0100, Harald Fuchs <hf1110x(at)protecting(dot)net> wrote:
> In article <b42b73150701230831t317595f6o3beb37d43f363412(at)mail(dot)gmail(dot)com>,
> "Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
>
> > can anybody think of of a way to sneak these into dollar quoted
> > strings for substitution into create function?
>
> Can't you put the psql call into a shell script and use shell variable
> substitution for that?
right. that works, actually I was using gcc to preprocess my sql
files. This has some side benefits: with a little work you can
actually have C code (or php or whatever) and sql scripts share a
common header, but you can no longer paste sql into psql which is
basically how I like to develop.
psql variables sidestep that tradeoff but are not usable inside
function definitions which is a critical drawback. This is on top of
the fact that create function takes a string but not a string
expression, so you can't run translate() and the like on it.
I'm wondering if I can use some tricky variable substition using sed
or something similar but I'm drawing a blank at the moment.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-01-24 01:30:50 | Re: [1/2 OFF] Varlena.com inaccessible from .br (Blocked?) |
Previous Message | Jorge Godoy | 2007-01-24 00:52:14 | Re: [1/2 OFF] Varlena.com inaccessible from .br (Blocked?) |