Re: Additional psql requirements - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: Additional psql requirements
Date
Msg-id 20080725094741.737E.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Additional psql requirements  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Additional psql requirements  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> wrote:

> * access to version number
> * simple mechanism for conditional execution
> * ability to set substitution variables from command execution
> * conditional execution whether superuser or not

Can we use pgScript for such flow controls?
http://pgscript.projects.postgresql.org/INDEX.html

I'm not sure pgScript can be used in pgAdmin already, but if we support
it both psql and pgAdmin, the scripting syntax will be a defact standard
because they are the most major user interfaces to postgres. I think it is
not good to add another "dialect" that can be used only in psql.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_dump vs data-only dumps vs --disable-triggers
Next
From: "Josh Tolley"
Date:
Subject: Re: Do we really want to migrate plproxy and citext into PG core distribution?