Re: plpgsql defensive mode - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: plpgsql defensive mode
Date
Msg-id CAFj8pRApvKppVFDZbX1D6GK++Mm6-4gyHFBjV-koNEeHefTfyQ@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql defensive mode  (Marko Tiikkaja <marko@joh.to>)
Responses Improving PL/PgSQL (was: Re: plpgsql defensive mode)
List pgsql-hackers



2014-09-06 19:54 GMT+02:00 Marko Tiikkaja <marko@joh.to>:
On 2014-09-06 7:50 PM, Pavel Stehule wrote:
2014-09-06 16:31 GMT+02:00 Marko Tiikkaja <marko@joh.to>:
How do you run queries which affect more than one row in this mode?
Because that's crucial as well.  We want something we can run 100% of our
code on, but with a slightly more convenient syntax than PL/PgSQL provides
right when coding defensively in the cases where exactly one row should be
affected.


you use a normal function. I don't expect, so it can be too often in your
case.

Then that doesn't really solve our problem.  Switching between two languages on a per-function basis, when both look exactly the same but have very different semantics would be a nightmare.

It is maximum what is possible

use a different language instead

Pavel

 


.marko

pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: plpgsql defensive mode
Next
From: Marko Tiikkaja
Date:
Subject: Re: proposal: plpgsql - Assert statement