| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to> |
| Subject: | Re: Assertions in PL/PgSQL |
| Date: | 2013-09-15 21:23:32 |
| Message-ID: | CAJKUy5g85ps__Z2tP+fbLJcWWg10MqFefhOj2uMCcnrCxWC1AA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
El 14/09/2013 15:25, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> escribió:
>
> Hello
>
> There is a significant issue - new reserved keyword. There is high
probability so lot of users has a functions named "assert".
>
> I like this functionality, but I dislike any compatibility break for
feature, that can be implemented as extension without any lost of
compatibility or lost of functionality.
>
> So can you redesign this without new keyword?
>
Hi,
If using ASSERT as keyword is not acceptable, not that i agree but in case.
What about using RAISE EXCEPTION WHEN (condition)
--
Jaime Casanova
2ndQuadrant: Your PostgreSQL partner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2013-09-15 21:52:48 | Re: Where to load modules from? |
| Previous Message | Andrew Gierth | 2013-09-15 17:58:00 | [Review] Effectiveness of enable_material = off |