Re: Additional psql requirements
От | daveg |
---|---|
Тема | Re: Additional psql requirements |
Дата | |
Msg-id | 20080725075223.GN24049@sonic.net обсуждение исходный текст |
Ответ на | Re: Additional psql requirements (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: Additional psql requirements
|
Список | pgsql-hackers |
On Fri, Jul 25, 2008 at 08:16:59AM +0100, Simon Riggs wrote: > > 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. It seems to me that a sql-like client side scripting language should be as similar as possible to plpgsql. Pgscript looks a bit like plpgsql, but is pretty much incompatible with it for no particularly obvious reason. -dg -- David Gould daveg@sonic.net 510 536 1443 510 282 0869 If simplicity worked, the world would be overrun with insects.
В списке pgsql-hackers по дате отправления: