Re: Additional psql requirements - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Additional psql requirements
Date
Msg-id 1216970219.3894.849.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Additional psql requirements  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Additional psql requirements  (daveg <daveg@sonic.net>)
Re: Additional psql requirements  ("Pavel Stehule" <pavel.stehule@gmail.com>)
List pgsql-hackers
On Fri, 2008-07-25 at 10:00 +0900, ITAGAKI Takahiro wrote:
> 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.

I just want good way, not two imperfect ones.

And I'm not going to suggest having pgscript in core.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: "Asko Oja"
Date:
Subject: Re: Do we really want to migrate plproxy and citext into PG core distribution?
Next
From: Simon Riggs
Date:
Subject: Re: pg_dump vs data-only dumps vs --disable-triggers