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

From Marko Tiikkaja
Subject Re: PL/PgSQL STRICT
Date
Msg-id 50D485D0.5050201@joh.to
Whole thread Raw
In response to Re: PL/PgSQL STRICT  (Marko Tiikkaja <pgmail@joh.to>)
Responses Re: PL/PgSQL STRICT
Re: PL/PgSQL STRICT
List pgsql-hackers
On 12/21/12 4:49 PM, I wrote:
> 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:

I realize I didn't really answer the question.

The use case is when you're UPDATEing or DELETEing a row and you want to 
quickly assert that there should be exactly one row.  For example, if 
you've previously locked a row with SELECT .. FOR UPDATE, and now you 
want to UPDATE or DELETE it, it better be there (or you have a bug 
somewhere).


Regards,
Marko Tiikkaja




pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: PL/PgSQL STRICT
Next
From: Tom Lane
Date:
Subject: Re: need a function to extract list items from pg_node_tree