| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jan Wieck <jan(at)wi3ck(dot)info> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: plpgsql - Assert statement |
| Date: | 2014-09-17 18:56:05 |
| Message-ID: | 5419D945.3000400@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/16/14 12:01 AM, Alvaro Herrera wrote:
> Jan Wieck wrote:
>> I think that most data integrity issues can be handled by a well
>> designed database schema that uses UNIQUE, NOT NULL, REFERENCES and
>> CHECK constraints. Assertions are usually found inside of complex
>> code constructs to check values of local variables. I don't think it
>> is even a good idea to implement assertions that can query arbitrary
>> data.
>
> Actually Peter Eisentraut posted a patch for SQL assertions:
> http://www.postgresql.org/message-id/1384486216.5008.17.camel@vanquo.pezone.net
SQL assertions are just a kind of CHECK constraint, so fully
Jan-compliant. ;-)
I don't mind PL/pgSQL having an "assert" statement like many programming
languages, but I find a lot of the proposed details dubious.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2014-09-17 19:00:33 | Re: proposal: plpgsql - Assert statement |
| Previous Message | Emanuel Calvo | 2014-09-17 18:41:55 | Re: Turning off HOT/Cleanup sometimes |