Jonah,
Thanks for your comments.
Jonah H. Harris writes:
> I have a lot of shell scripts that run as cron jobs and have considered
> this option. However, if you look at it carefully, SQL is totally
> different from say perl, php, bash, etc. for scripts which execute from
> the shell. To
Brook,
I have a lot of shell scripts that run as cron jobs and have considered
this option. However, if you look at it carefully, SQL is totally
different from say perl, php, bash, etc. for scripts which execute from
the shell. Tom is right, it is much more valuable and supportable to
call
Tom Lane writes:
> Given that # is not a comment introducer in SQL, I would consider
> it a bug if it did.
I understand that # is not a comment introducer in SQL. I am
wondering if it would be sensible to introduce an exception for the
first line of a file. To prevent problems the behavior sho
<[EMAIL PROTECTED]> writes:
> I would like to use pgsl as an interpreter (in the sense of
> execve(2)). In short, if a file begins with the line
>#! /path/to/psql -f
> it should be interpretable by psql. The normal semantics of execve(2)
> ensure that this will work perfectly (indee
I would like to use pgsl as an interpreter (in the sense of
execve(2)). In short, if a file begins with the line
#! /path/to/psql -f
it should be interpretable by psql. The normal semantics of execve(2)
ensure that this will work perfectly (indeed a file containing
"#!/path/to/psql
