Re: Additional psql requirements - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Additional psql requirements
Date
Msg-id 1216976225.3894.868.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Additional psql requirements  ("Dave Page" <dpage@pgadmin.org>)
Responses Re: Additional psql requirements  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.stehule@gmail.com> wrote:
> > 2008/7/25 Dave Page <dpage@pgadmin.org>:
> >> On Fri, Jul 25, 2008 at 8:52 AM, daveg <daveg@sonic.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.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Bjorn Munch
Date:
Subject: Whence cometh the data in src/test/regress/data/streets.data ?
Next
From: ITAGAKI Takahiro
Date:
Subject: Re: Uncopied parameters on CREATE TABLE LIKE