From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pl/pgsql: END verbosity |
Date: | 2005-06-22 02:49:51 |
Message-ID: | 200506211949.51916.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Neil,
> In PL/PgSQL, "END LOOP" is used to terminate loop blocks, and "END IF"
> is used to terminate IF blocks. This is needlessly verbose: we could
> simply accept "END" in both cases without syntactic ambiguity. I'd like
> to make this change, so that END can be used to terminate any kind of
> block. There's no need to remove support for the present syntax, of
> course, so there's no backward compatibility concern. Oracle's PL/SQL
> does require "END IF" and "END LOOP", but folks interested in maximum
> compatibility can always use those forms if they like.
No problem from me. Since the parser checks for block closure for all
block types, I can't see how this would be a problem.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2005-06-22 02:56:18 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |
Previous Message | Tom Lane | 2005-06-22 02:45:55 | Re: The contrib hit list |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2005-06-22 02:56:18 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |
Previous Message | Neil Conway | 2005-06-22 02:17:42 | pl/pgsql: END verbosity |