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.
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2002-04-26 15:20:52|
|Subject: Re: Vote totals for SET in aborted transaction |
|Previous:||From: Tom Lane||Date: 2002-04-26 15:10:18|
|Subject: Re: PSQL \x \l command issues |