Re: Additional psql requirements

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: daveg <daveg(at)sonic(dot)net>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "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:40:59
Message-ID: 937d27e10807250140x1e28edc6iec5986987db74917@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bjorn Munch 2008-07-25 08:50:07 Whence cometh the data in src/test/regress/data/streets.data ?
Previous Message Pavel Stehule 2008-07-25 08:36:53 Re: Additional psql requirements