Re: Assertions in PL/PgSQL - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: Assertions in PL/PgSQL
Date
Msg-id CAJKUy5g85ps__Z2tP+fbLJcWWg10MqFefhOj2uMCcnrCxWC1AA@mail.gmail.com
Whole thread Raw
In response to Re: Assertions in PL/PgSQL  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Assertions in PL/PgSQL
List pgsql-hackers
<p><br /> El 14/09/2013 15:25, "Pavel Stehule" <<a
href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>>escribió:<br /> ><br /> > Hello<br />
><br/> > There is a significant issue - new reserved keyword. There is high probability so lot of users has a
functionsnamed "assert". <br /> ><br /> > 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.<br /> ><br
/>> So can you redesign this without new keyword?<br /> ><p>Hi,<p>If using ASSERT as keyword is not acceptable,
notthat i agree but in case. What about using RAISE EXCEPTION WHEN (condition)<p>--<br /> Jaime Casanova<br />
2ndQuadrant:Your PostgreSQL partner  

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: [Review] Effectiveness of enable_material = off
Next
From: Jeff Janes
Date:
Subject: Re: Where to load modules from?