Re: PL/pgSQL 1.2 - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: PL/pgSQL 1.2
Date
Msg-id 54086B51.3040300@wi3ck.info
Whole thread Raw
In response to Re: PL/pgSQL 1.2  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: PL/pgSQL 1.2  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 09/04/2014 09:31 AM, Pavel Stehule wrote:
> 2014-09-04 15:24 GMT+02:00 Jan Wieck <jan@wi3ck.info
>
>     I think I like the COMMAND CONSTRAINT the best so far.
>
>
> I not, because when it will not be part of SQL, than parser in plpgsql
> will be more complex. You have to inject SELECT, UPDATE, INSERT, DELETE

Making the COMMAND CONSTRAINT part of the core SQL parser was how I 
understood Hannu's idea. It would be horrible to tuck that feature away 
inside of a PL, rather than making it available to all PLs as well as 
applications, that use SQL directly (I think there still are two or 
three applications that do).


Regards,
Jan

-- 
Jan Wieck
Senior Software Engineer
http://slony.info



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Escaping from blocked send() reprised.
Next
From: Pavel Stehule
Date:
Subject: Re: PL/pgSQL 1.2