Re: Proposal - Continue stmt for PL/pgSQL

From: "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal - Continue stmt for PL/pgSQL
Date: 2005-06-16 18:51:45
Message-ID: 42B1CA41.3030100@tvi.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

As a near-daily PL/pgSQL developer, I similarly agree.

-Jonah

Andrew Dunstan wrote:

>
>
> Pavel Stehule wrote:
>
>>
>> What do you think about it? It's broke PL/SQL compatibility, I know,
>> but via last discussion I have opinion so Oracle compatibility isn't
>> main objective PL/pgSQL. There is some less/bigger diferencess:
>> SQLSTATE, EXCEPTION from my last proposal, atd.
>>
>>
>>
>>
>
> Well, yes, but I don't think we should break compatibility
> arbitrarilly. I guess it could be argued that this is a missing
> feature in PL/SQL and its Ada parent - implementing GOTO just to
> handle this case seems unnecessary.
>
> I agree with Tom that it should only be allowed inside a loop.
>
> cheers
>
> andrew
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2005-06-16 19:00:04 Re: PROPOSAL - User's exception in PL/pgSQL
Previous Message Hannu Krosing 2005-06-16 18:42:13 Re: Autovacuum in the backend