X-Original-To: pgsql-sql-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id D96159FB332
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 21 Sep 2006 01:54:29 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 94752-07-2 for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 21 Sep 2006 04:54:18 +0000 (UTC)
X-Greylist: delayed 00:06:39.317074 by SQLgrey-
Received: from web8318.mail.in.yahoo.com (web8318.mail.in.yahoo.com
	[202.43.219.53]) by postgresql.org (Postfix) with SMTP id 065229FB32F
	for <pgsql-sql@postgresql.org>; Thu, 21 Sep 2006 01:54:16 -0300 (ADT)
Received: (qmail 59404 invoked by uid 60001); 21 Sep 2006 04:47:34 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=UllypgUa1q69mjJDVdYYOYlqLBwu82HREjmRLQsHNfcByazRpxRttEZl3QqpdqGkjj/xJ793JbjFd4azYQYt6tsamaLkv8kBchQBv/VV8k6hmnkeNgb6rMSCPXkbHFSpVEVcWSgFgg3qKNaTM20CBE8BN9g7aYWVj6HWA/AufMw=
	;
Message-ID: <20060921044734.59402.qmail@web8318.mail.in.yahoo.com>
Received: from [202.142.82.85] by web8318.mail.in.yahoo.com via HTTP;
	Thu, 21 Sep 2006 05:47:34 BST
Date: Thu, 21 Sep 2006 05:47:34 +0100 (BST)
From: vijay balan <vijay_gensec@yahoo.co.in>
Subject: UnSubscribe
To: pgsql-sql@postgresql.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-2525928-1158814054=:39892"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE
X-Spam-Level: 
X-Archive-Number: 200609/144
X-Sequence-Number: 26355

--0-2525928-1158814054=:39892
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit



gould@embl.de wrote:  Date: Fri, 15 Sep 2006 11:16:06 +0200
From: gould@embl.de
To: pgsql-sql@postgresql.org
Subject: [SQL] Omission of 'FROM' ? diff between pgsql 7.4.1 and pgsql 8.1.4

hi
I am upgrading from pgsql 7.4.1 to pgsql 8.1.4. However, some of the application
queries won't run on the newer version of pgsql.
An example of the type of query is:

SELECT
protein_external_links.protein_id, external_links.external_id,
proteins.public_name
WHERE
protein_external_links.external_link_id = external_links.id and
protein_external_links.protein_id = proteins.id and
external_links.external_database_id != 8 and
external_links.external_id_type_id = 2;

on pgsql7.4.1 what tables need to be queried seems to be implicitly deduced from
the rest of the SQL without the need for a FROM clause.
However, on pgsql 8.1.4 the following error is given:
ERROR: missing FROM-clause entry for table "protein_external_links"

Is there some query optimization config setting I can set in pgsql 8.1.4 to fix
this problem rather than having to change the queries in the code? I've read
over the changes between pgsql 7 and pgsql 8 but nothing seems to stand out to
me as referencing this problem. Anyone with more knowledge that can point me in
the right direction?

Thanks
Kate

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match


 				
---------------------------------
 Find out what India is talking about on  - Yahoo! Answers India 
 Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
--0-2525928-1158814054=:39892
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<BR><BR><B><I>gould@embl.de</I></B> wrote:  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Date: Fri, 15 Sep 2006 11:16:06 +0200<BR>From: gould@embl.de<BR>To: pgsql-sql@postgresql.org<BR>Subject: [SQL] Omission of 'FROM' ? diff between pgsql 7.4.1 and pgsql 8.1.4<BR><BR>hi<BR>I am upgrading from pgsql 7.4.1 to pgsql 8.1.4. However, some of the application<BR>queries won't run on the newer version of pgsql.<BR>An example of the type of query is:<BR><BR>SELECT<BR>protein_external_links.protein_id, external_links.external_id,<BR>proteins.public_name<BR>WHERE<BR>protein_external_links.external_link_id = external_links.id and<BR>protein_external_links.protein_id = proteins.id and<BR>external_links.external_database_id != 8 and<BR>external_links.external_id_type_id = 2;<BR><BR>on pgsql7.4.1 what tables need to be queried seems to be implicitly deduced from<BR>the rest of the SQL without the need for a FROM clause.<BR>However,
 on pgsql 8.1.4 the following error is given:<BR>ERROR: missing FROM-clause entry for table "protein_external_links"<BR><BR>Is there some query optimization config setting I can set in pgsql 8.1.4 to fix<BR>this problem rather than having to change the queries in the code? I've read<BR>over the changes between pgsql 7 and pgsql 8 but nothing seems to stand out to<BR>me as referencing this problem. Anyone with more knowledge that can point me in<BR>the right direction?<BR><BR>Thanks<BR>Kate<BR><BR>---------------------------(end of broadcast)---------------------------<BR>TIP 9: In versions below 8.0, the planner will ignore your desire to<BR>choose an index scan if your joining column's datatypes do not<BR>match<BR></BLOCKQUOTE><BR><p>&#32;
	

	
		<hr size=1></hr> 
Find out what India is talking about on  - <a href="http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/">Yahoo! Answers India</a> <BR> 
Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. <a href="http://us.rd.yahoo.com/mail/in/messengertagline/*http://in.messenger.yahoo.com">Get it NOW</a>
--0-2525928-1158814054=:39892--