| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Jan Wieck <jan(at)wi3ck(dot)info>, 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 19:04:55 |
| Message-ID: | CAFj8pRCCJq5jn4TtWvn01FMs6fzzvuMsxxHO4bXf-eqr-vcrVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014-09-17 21:00 GMT+02:00 Peter Eisentraut <peter_e(at)gmx(dot)net>:
> On 9/14/14 2:49 PM, Jan Wieck wrote:
> > I don't think it is even a good idea to implement assertions that can
> > query arbitrary data.
>
> In a normal programming language, an assertion is usually a static fault
> in your program. If the assertion ever fails, you fix your program and
> then it hopefully never happens again.
>
> Assertion that query the state of the database or result row counts are
> pushing that concept quite a bit. Those are not assertions, those are
> just plain old error handling.
>
>
What is difference between content of variable or content of database? You
can test any prerequisite, but when this prerequisite is not solved, than
exception is very very hard without possible handling.
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Szymon Guz | 2014-09-17 19:26:48 | Re: printing table in asciidoc with psql |
| Previous Message | Marko Tiikkaja | 2014-09-17 19:04:53 | Re: proposal: plpgsql - Assert statement |