| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Additional psql requirements |
| Date: | 2008-07-25 07:16:59 |
| Message-ID: | 1216970219.3894.849.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2008-07-25 at 10:00 +0900, ITAGAKI Takahiro wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-07-25 07:24:36 | Re: pg_dump vs data-only dumps vs --disable-triggers |
| Previous Message | Asko Oja | 2008-07-25 06:37:27 | Re: Do we really want to migrate plproxy and citext into PG core distribution? |