From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
---|---|
To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: proposal for 8.4: PL/pgSQL - statement CASE |
Date: | 2008-01-17 19:41:37 |
Message-ID: | 37ed240d0801171141i7da3936o798a511b951bc689@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 18, 2008 3:19 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> > Isn't there a danger of syntactical conflict with the SQL SELECT ... CASE
> > statement?
>
> no, isn't. SELECT CASE can be only in expression .. inside SQL
> statement, but PL/SQL CASE is PL statement. These are two different
> worlds. SELECT CASE is invisible for pl parser, because pl parser
> solves statements, not expressions.
>
Sounds good. Chaining ELSIFs is ugly; I've wished for something like
this in PL/pgSQL from time to time while writing my functions.
A hearty "+1" from me. Let me know if there's anything I can do to
help move it forward.
Cheers
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2008-01-17 19:53:13 | Re: Thick indexes - a look at count(1) query |
Previous Message | Kevin Grittner | 2008-01-17 19:35:01 | Re: OUTER JOIN performance regression remains in 8.3beta4 |