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

From Tom Lane
Subject Re: PL/PgSQL STRICT
Date
Msg-id 16397.1356106923@sss.pgh.pa.us
Whole thread Raw
In response to Re: PL/PgSQL STRICT  (Marko Tiikkaja <pgmail@joh.to>)
Responses Re: PL/PgSQL STRICT  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: PL/PgSQL STRICT  (Marko Tiikkaja <pgmail@joh.to>)
Re: PL/PgSQL STRICT  (Joel Jacobson <joel@trustly.com>)
List pgsql-hackers
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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: "David Johnston"
Date:
Subject: Re: PL/PgSQL STRICT
Next
From: Charles Gomes
Date:
Subject: Writing Trigger Functions in C