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

From Marko Tiikkaja
Subject Re: PL/PgSQL STRICT
Date
Msg-id 50D48F17.7040705@joh.to
Whole thread Raw
In response to Re: PL/PgSQL STRICT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/21/12 5:22 PM, Tom Lane wrote:
> Marko Tiikkaja <pgmail@joh.to> writes:
>> Another idea would be to force the STRICT to be immediately after
>> INSERT, UPDATE or DELETE.
>
> What about before it, ie
>
>     STRICT UPDATE ...
>
> This should dodge the problem of possible conflict with table names,
> and it seems to me to read more naturally too.

Yeah, putting STRICT after the command wouldn't work for UPDATE.

I like this one best so far, so I'm going with this syntax for the next 
version of the patch.



Regards,
Marko Tiikkaja



pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: PL/PgSQL STRICT
Next
From: Dimitri Fontaine
Date:
Subject: Re: Event Triggers: adding information