X-Original-To: pgsql-sql@postgresql.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id C2AB7475F6A
	for <pgsql-sql@postgresql.org>; Fri,  2 May 2003 12:14:22 -0400 (EDT)
Received: from davinci.ethosmedia.com (unknown [209.10.40.251])
	by postgresql.org (Postfix) with ESMTP id 80DE947638D
	for <pgsql-sql@postgresql.org>; Fri,  2 May 2003 12:14:10 -0400 (EDT)
Received: from [63.195.55.98] (HELO spooky)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2)
	with ESMTP id 3003365; Fri, 02 May 2003 09:14:03 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Tomasz Myrta <jasiek@klaster.net>, alien@spaceship.com
Subject: Re: implied FROM
Date: Fri, 2 May 2003 09:13:36 -0700
User-Agent: KMail/1.4.3
Cc: pgsql-sql@postgresql.org
References: <34943.24.243.219.116.1051841197.squirrel@earth.spaceship.com>
	<3EB21AE6.4020205@klaster.net>
In-Reply-To: <3EB21AE6.4020205@klaster.net>
MIME-Version: 1.0
Message-Id: <200305020913.36152.josh@agliodbs.com>
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	REPLY_WITH_QUOTES,USER_AGENT_KMAIL autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Archive-Number: 200305/30
X-Sequence-Number: 13195

Tomasz,

> There was a discussion several months ago about "missing from clause". I
> was voting for changing this warning into exception. Some people said,
> that it is very useful inside update queries. The conclusion was this
> behaviour should stay as it is. Anyway it isn't such a big problem for
> me, because the only problem is to catch "missing from clause" warning.

You'll be happy to know that Nigel Andrews just this week submitted a patch=
 to=20
the 7.4 source which makes "missing from clause" a GUC option that defaults=
=20
to true.   So in future versions you will be able to set it to false, and=
=20
Postgres will throw you a fatal exception instead of assuming which data yo=
u=20
want.

--=20
Josh Berkus
Aglio Database Solutions
San Francisco