Re: proposal for 8.4: PL/pgSQL - statement CASE - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal for 8.4: PL/pgSQL - statement CASE
Date
Msg-id 162867790801170900v6eb012a0vf9e23f807fa89007@mail.gmail.com
Whole thread Raw
In response to Re: proposal for 8.4: PL/pgSQL - statement CASE  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: proposal for 8.4: PL/pgSQL - statement CASE  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
>
> A. I could give flying donkey butt about being the Oracle-Compatible
> community.
>
> B. That "SWITCH" may be an alternate syntax because 15 years ago when I
> took a CS class and I did one chapter of C they had a SWITCH statement
> that resembles CASE.
>

Primary goal is ANSI SQL conformance (for me). Current PL/pgSQL isn't
compatible and it will not be compatible in future (we have different
implementation of SRF and really specific implementation of OUT
parameters). But why artificially create bigger dif between PL/pgSQL
and PL/SQL?

I am sorry, I can't to speak in English gently (because my English is
all else than English), and some my notes are maybe too much hard.

Pavel



> Please continue on.
>
> Sincerely,
>
> Joshua D. Drake
>
> - --
> The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
> Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
> Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHj4hVATb/zqfZUUQRAhbpAJ9+qwBAHqxwSCCeVzbRjKBiFTpVhQCdEX+j
> vrXiUgBeLQoBKx3s68214qw=
> =kc7c
> -----END PGP SIGNATURE-----
>


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: proposal for 8.4: PL/pgSQL - statement CASE
Next
From: "Joshua D. Drake"
Date:
Subject: Re: proposal for 8.4: PL/pgSQL - statement CASE