| From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
|---|---|
| To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Josh Berkus <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Nested Transactions, Abort All |
| Date: | 2004-07-09 16:03:38 |
| Message-ID: | Pine.LNX.4.44.0407091755110.32281-100000@kix.fsv.cvut.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> An 'END SUB' after a 'BEGIN SUB' in plpgsql could be required, and could
> mean start/end block and subtx. I do not really see a downside.
> But, it would imho only make sense if the 'END SUB' would commit sub
> or abort sub iff subtx is in aborted state (see my prev posting)
>
> Andreas
>
Hello,
is good idea use keywords "begin sub" and "end sub"? Programmers like me
will be an problems with reading and writing SP, because begin sub and
mostly end sub are keywords from visual basic with different sense.
BEGIN SUBTRANSACTION and END SUBTRANSACTION is longer but more readable
regards
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2004-07-09 16:04:01 | Re: User Quota Implementation |
| Previous Message | Alvaro Herrera | 2004-07-09 15:47:51 | Re: Nested Transactions, Abort All |