Horton

Re: Vote totals for SET in aborted transaction

Jan Wieck <janwieck@yahoo.com>

View thread View on postgr.es
From: Jan Wieck <janwieck@yahoo.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jan Wieck <janwieck@yahoo.com>, "Marc G. Fournier" <scrappy@hub.org>, Vince Vielhaber <vev@michvhf.com>, Mike Mascari <mascarm@mascari.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2002-04-26T15:15:08Z
Lists: pgsql-hackers 
Bruce Momjian wrote:
> So you do see a difference between SET and DROP TABLE because the second
> is a utility command. OK, I'll buy that, but my point was different.
>
> My point was that we don't match Oracle for DROP TABLE, so why is
> matching for SET so important?

    Good  point,  I  never  understood the compatibility issue on
    this level either. Applications that  create/drop  tables  at
    runtime  are  IMNSVHO  self-modifying  code.  Thus,  I  don't
    consider it a big porting issue.   Applications  that  do  it
    should be "replaced", not ported.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #