| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] END/ABORT |
| Date: | 2000-01-29 15:59:21 |
| Message-ID: | 14755.949161561@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>>>> I'd like to yank the END/ABORT commands, since they're non-standard and
>>>> redundant (COMMIT/ROLLBACK). Anyone who could not bear to see them go?
>>
>> Exactly what will this accomplish, other than breaking a lot of existing
>> applications? (Including all of mine, which no doubt biases my thinking.)
> Okay, I was just wondering. But I'm going to change all the notices and
> docs to use commit and rollback instead.
OK, that seems fair enough.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-01-29 16:24:58 | Re: [HACKERS] select count(*) from hits group by count; |
| Previous Message | Tom Lane | 2000-01-29 15:58:37 | Re: [HACKERS] TODO list check |