2008/7/25 Simon Riggs <[EMAIL PROTECTED]>: > > On Fri, 2008-07-25 at 10:00 +0900, ITAGAKI Takahiro wrote: >> Simon Riggs <[EMAIL PROTECTED]> 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. + 1
pgScript is too heavy for most purposes is enough some like \for select * from information_schema.tables grant read on $1 to public; \endfor regards Pavel Stehule > > -- > Simon Riggs www.2ndQuadrant.com > PostgreSQL Training, Services and Support > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
