Re: PL/PgSQL STRICT - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: PL/PgSQL STRICT
Date
Msg-id 50D48511.8020001@joh.to
Whole thread Raw
In response to Re: PL/PgSQL STRICT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PL/PgSQL STRICT  (Marko Tiikkaja <pgmail@joh.to>)
Re: PL/PgSQL STRICT  (Marko Tiikkaja <pgmail@joh.to>)
List pgsql-hackers
On 12/21/12 4:39 PM, Tom Lane wrote:
> What is the use-case for this?

Currently, the way to do this would be something like:

DECLARE  _ok bool;
BEGIN
UPDATE foo .. RETURNING TRUE INTO STRICT _ok;

We have a lot of code like this, and I bet others do as well.

> Won't this result in the word STRICT
> becoming effectively reserved in contexts where it currently is not?

It will, which probably is not ideal if it can be avoided.  I also 
considered syntax like  INTO STRICT NULL,  but that felt a bit ugly.  It 
would be great if someone had any smart ideas about the syntax.


Regards,
Marko Tiikkaja



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Review of Row Level Security
Next
From: Marko Tiikkaja
Date:
Subject: Re: PL/PgSQL STRICT