From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, daveg <daveg(at)sonic(dot)net>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Additional psql requirements |
Date: | 2008-07-25 08:57:05 |
Message-ID: | 1216976225.3894.868.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2008-07-25 at 09:40 +0100, Dave Page wrote:
> On Fri, Jul 25, 2008 at 9:36 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> > 2008/7/25 Dave Page <dpage(at)pgadmin(dot)org>:
> >> On Fri, Jul 25, 2008 at 8:52 AM, daveg <daveg(at)sonic(dot)net> wrote:
> >>
> >>> 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.
> >>
> >> pgScript originally used a c-like syntax when it was pgUnitTest iirc.
> >> The new version is designed to be familiar to users of T-SQL.
> >
> > it is little bit unhappy - it's like T-SQL, but it isn't T-SQL - and
> > it's far to plpgsql
>
> I see no point in replicating pl/pgsql. Better to implement anonymous
> blocks in the server for that.
Agreed. My suggestion was for something much simpler than either.
Complex logic can be done in functions.
I just wanted an easy way to write install scripts that work on various
releases/schemas/environments, works on core and on any platform.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2008-07-25 08:57:35 | Re: Uncopied parameters on CREATE TABLE LIKE |
Previous Message | Bjorn Munch | 2008-07-25 08:50:07 | Whence cometh the data in src/test/regress/data/streets.data ? |