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

From Joshua D. Drake
Subject Re: proposal for 8.4: PL/pgSQL - statement CASE
Date
Msg-id 20080117090845.1284ab3b@commandprompt.com
Whole thread Raw
In response to Re: proposal for 8.4: PL/pgSQL - statement CASE  ("Pavel Stehule" <pavel.stehule@gmail.com>)
Responses Re: proposal for 8.4: PL/pgSQL - statement CASE
Re: proposal for 8.4: PL/pgSQL - statement CASE
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 17 Jan 2008 18:00:21 +0100
"Pavel Stehule" <pavel.stehule@gmail.com> wrote:

> 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.

If primary goal is ANSI SQL conformance shouldn't we be focusing on
pl/psm not plpgsql? (yes I am aware they are similar syntatically)

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)

iD8DBQFHj4udATb/zqfZUUQRAgyeAJ9Cb9pAMiWvP/JDv6F89JPBAh2IPACeI6a6
0yl+dXdE9XyCEoGNCeb9EXw=
=oHVb
-----END PGP SIGNATURE-----

pgsql-hackers by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: proposal for 8.4: PL/pgSQL - statement CASE
Next
From: "Merlin Moncure"
Date:
Subject: Re: proposal for 8.4: PL/pgSQL - statement CASE