Thread: END/ABORT
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.) -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
[Charset ISO-8859-1 unsupported, filtering to ASCII...] > 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.) > We have to keep them in there for compatibility with older code. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
> I'd like to yank the END/ABORT commands, since they're non-standard and > redundant (COMMIT/ROLLBACK). Anyone who couldnot bear to see them go? > (Of course END would stay as a reserved word.) We have to keep them in there for compatibility with older code. But documentation could mark them as deprecated so new users will use the standard commands. Cheers, Brook
> > 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.) > > We have to keep them in there for compatibility with older code. > > But documentation could mark them as deprecated so new users will use > the standard commands. Yes, I think that is done, but am not positive. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
Peter Eisentraut <peter_e@gmx.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.)
> (Of course END would stay as a reserved word.)
If the words must remain reserved, then there's even less value in
removing the statements.
I'm agin it...
regards, tom lane
On 2000-01-28, Tom Lane mentioned: > Peter Eisentraut <peter_e@gmx.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. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
Peter Eisentraut <peter_e@gmx.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
On 2000-01-28, Bruce Momjian mentioned: > [Charset ISO-8859-1 unsupported, filtering to ASCII...] > > 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.) > > > > We have to keep them in there for compatibility with older code. > Okay, maybe yank was the wrong word. But I changed the command tags to commit/rollback and the notices to something friendlier. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
[Charset ISO-8859-1 unsupported, filtering to ASCII...] > On 2000-01-28, Tom Lane mentioned: > > > Peter Eisentraut <peter_e@gmx.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. Great. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
Bruce Momjian 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.) > > > > We have to keep them in there for compatibility with older code. How long? IIRC, CURRENT has been replaced by OLD after I've fixed the rewriter. Both have been there between 6.4 and 6.5. With6.5 CURRENT was gone. Of course, removing END/ABORT will touch many applications using transactions, but I would vote for it anyway, since it's standard. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #========================================= wieck@debis.com (Jan Wieck) #
At 09:41 AM 1/31/00 +0100, Jan Wieck wrote: > Of course, removing END/ABORT will touch many applications > using transactions, but I would vote for it anyway, since > it's standard. Does it make all that much sense to worry about the actual word used when the need to use "begin" is non-standard to begin with? Of course, removing that would REALLY impact current applications... - Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert Serviceand other goodies at http://donb.photo.net.
Don Baccus wrote: > At 09:41 AM 1/31/00 +0100, Jan Wieck wrote: > > > Of course, removing END/ABORT will touch many applications > > using transactions, but I would vote for it anyway, since > > it's standard. > > Does it make all that much sense to worry about the actual word > used when the need to use "begin" is non-standard to begin with? There is no explicit "BEGIN WORK" on SQL92, transaction initiation is always implicit and it terminates either with aCOMMIT or a ROLLBACK statement. > > > Of course, removing that would REALLY impact current applications... > > - Don Baccus, Portland OR <dhogaza@pacifier.com> > Nature photos, on-line guides, Pacific Northwest > Rare Bird Alert Service and other goodies at > http://donb.photo.net. > > ************ -- Jose' Soares Bologna, Italy Jose@sferacarta.com
At 02:19 PM 2/1/00 +0100, Jose Soares wrote: > > >Don Baccus wrote: >> Does it make all that much sense to worry about the actual word >> used when the need to use "begin" is non-standard to begin with? > > There is no explicit "BEGIN WORK" on SQL92, transaction initiation > is always implicit and it terminates either with a COMMIT or a >ROLLBACK > statement. That was my point, of course... - Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert Serviceand other goodies at http://donb.photo.net.