| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] END/ABORT |
| Date: | 2000-01-28 21:10:27 |
| Message-ID: | 3.0.1.32.20000128131027.00ec2da0@mail.pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 12:32 PM 1/28/00 -0800, Don Baccus wrote:
>At 06:54 PM 1/28/00 +0100, Peter Eisentraut wrote:
>>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?
>>(Of course END would stay as a reserved word.)
>I've got a lot of existing application code that has "end" in it...
>"begin" is non-standard, too...
Actually, to think again, for my application space (web toolkit) it
wouldn't be a problem because my rewrite of AOLserver's postgres
driver tracks transactions (both forms) and could easily issue
"COMMIT/ROLLBACK" in all cases. So I don't care :)
But, as Bruce points out, there's probably a fair amount of legacy
code out there that uses "END/ABORT"...
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-01-28 22:03:12 | Re: [HACKERS] END/ABORT |
| Previous Message | Don Baccus | 2000-01-28 20:32:48 | Re: [HACKERS] END/ABORT |