From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Harald Fuchs <hari(dot)fuchs(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql scripting tutorials |
Date: | 2008-09-11 15:55:15 |
Message-ID: | 20080911155515.GF9492@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Peter Eisentraut escribió:
> psql manual page:
>
> -c command
>
> --command command
> Specifies that psql is to execute one command string, command,
> and then exit. This is useful in shell scripts.
>
> command must be either a command string that is completely
> parsable by the server (i.e., it contains no psql specific
> features), or a single backslash command. Thus you cannot mix
> SQL and psql meta-commands with this option.
Doesn't say about variable expansion ... And it seems to be in a
different realm, because the point is that the command is going to have
a single destination (either \-processing or sending it to the server).
Is psql being just lazy here and avoiding parsing the command?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-09-11 15:55:28 | Re: declare column update expression |
Previous Message | Scott Marlowe | 2008-09-11 15:53:04 | Re: declare column update expression |