pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Christoph Haller <ch@rodos.fzk.de>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: Efficient DELETE Strategies
Date: Mon, 10 Jun 2002 15:41:37 -0700
Message-ID: <200206101541.37049.josh@agliodbs.com> (raw)
In-Reply-To: <8806.1023743276@sss.pgh.pa.us>
References: <200206101142.NAA16854@rodos>
	<j8u9gukf7882nq3tsfhqr5bte9386p637l@4ax.com>
	<8806.1023743276@sss.pgh.pa.us>


Tom,

> >> If so, what's their syntax?
> 
> > MSSQL seems to guess what the user wants.
> 
> Gack.  Nothing like treating mindless syntax variations as a "feature"
> list...

I vote that we stick to a strick SQL92 interpretation, here.   
1) It's standard
2) Strict syntax on DELETE statements is better.

Personally, I would *not* want the database to "guess what I want" in a delete 
statement; it might guess wrong and there go my records ...

Heck, one of the things I need to research how to turn off in PostgreSQL is 
the "Add missing FROM-clause" feature, which has tripped me up many times.  

-- 
-Josh Berkus




view thread (21+ messages)  latest in thread

Message-ID: <200206101541.37049.josh@agliodbs.com>
Permalink:  ../200206101541.37049.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200206101541.37049.josh@agliodbs.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, mkoi-pg@aon.at, ch@rodos.fzk.de, pgsql-hackers@postgresql.org
  Subject: Re: Efficient DELETE Strategies
  In-Reply-To: <200206101541.37049.josh@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox