Re: PL/PgSQL STRICT

From: Marko Tiikkaja <pgmail(at)joh(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/PgSQL STRICT
Date: 2012-12-21 15:49:37
Message-ID: 50D48511.8020001@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2012-12-21 15:52:48 Re: PL/PgSQL STRICT
Previous Message Simon Riggs 2012-12-21 15:41:00 Re: Review of Row Level Security