Re: proposal: plpgsql - Assert statement - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: plpgsql - Assert statement
Date
Msg-id CAFj8pRAHEwkBQhm2xfKUfMkp-JinDJoajjWA1+AZSQGvdn2QQg@mail.gmail.com
Whole thread Raw
In response to Re: proposal: plpgsql - Assert statement  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: proposal: plpgsql - Assert statement  (Jim Nasby <decibel@decibel.org>)
Re: proposal: plpgsql - Assert statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


2015-01-28 0:13 GMT+01:00 Jim Nasby <Jim.Nasby@bluetreble.com>:
On 1/27/15 1:30 PM, Pavel Stehule wrote:
    I don't see the separate warning as being helpful. I'd just do something like

    +                                (err_hint != NULL) ? errhint("%s", err_hint) : errhint("Message attached to failed assertion is null") ));


done


    There should also be a test case for a NULL message.


is there, if I understand well

I see it now. Looks good.

updated version with Jim Nasby's doc and rebase against last changes in plpgsql.

Regards

Pavel
 

--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

Attachment

pgsql-hackers by date:

Previous
From: Abhijit Menon-Sen
Date:
Subject: Re: Auditing extension for PostgreSQL (Take 2)
Next
From: Ashutosh Bapat
Date:
Subject: Re: inherit support for foreign tables