| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql Feature request \set query |
| Date: | 2008-10-23 08:29:03 |
| Message-ID: | 490035CF.3090804@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander wrote:
> If you want full scripting, look at pgscript, one of this summers gsoc
> projects. It'll ship in the next pgadmin and is also available as a
> standalone executable.
Yet another language?
What people asking for psql scriptability really want, in my estimate,
is the ability to write "SQL plus some control structures" anywhere, in
the server, in the client, or so that they don't have to know where.
Commercial vendors have that: Oracle has PL/SQL as server-side language
and client-side language. Microsoft has T-SQL. The others have similar
offerings.
What PostgreSQL has in one kind of extended SQL language in the
terminal, another kind of extended SQL language in the server (but
really two separate languages, one for functions, one outside of
functions), and now yet another kind of extended SQL language in the
GUI, each mutually wildly incompatible. And neither is based on a standard.
Something to think about ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-10-23 08:36:28 | Re: psql Feature request \set query |
| Previous Message | Peter Eisentraut | 2008-10-23 08:14:06 | Re: psql Feature request \set query |