| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql Feature request \set query |
| Date: | 2008-10-23 17:26:36 |
| Message-ID: | 4900B3CC.8090201@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Everyone,
> 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.
I'm *not* proposing to implement full scriptability in psql. Just one
obvious extension of the existing pgsql variable feature.
I agree that giving psql its own unique scripting language would be
stupid. We should use something existing. Ideally, we should make psql
pluggable with the Perl & Python debuggers.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-10-23 17:32:06 | Re: Block level concurrency during recovery |
| Previous Message | Heikki Linnakangas | 2008-10-23 17:24:11 | Re: Block level concurrency during recovery |