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:52:48
Message-ID: 50D485D0.5050201@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-12-21 15:53:26 Re: need a function to extract list items from pg_node_tree
Previous Message Marko Tiikkaja 2012-12-21 15:49:37 Re: PL/PgSQL STRICT