Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.2/8.9.1) with ESMTP id KAA52767
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 22 Feb 1999 10:50:45 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA08740;
	Mon, 22 Feb 1999 10:49:33 -0500 (EST)
To: philip.shiels@jrc.it
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Tables names from query 
In-reply-to: Your message of Mon, 22 Feb 1999 14:26:37 +0100
	<36D15B0D.B57DB69C@jrc.it>
Date: Mon, 22 Feb 1999 10:49:33 -0500
Message-ID: <8738.919698573@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Philip Shiels <philip.shiels@jrc.it> writes:
> I'm currently developing a postgres DB backend to my current project and have
> the following problem. If I execute a query I need to know the table the
> returning fields belong to. For example :

> SELECT x.y, z.y from x, y where x.key = z.key

Can you use "SELECT AS"?  For instance

	SELECT x.y AS x_y, z.y AS z_y WHERE ...

A bit grotty, but there's no hope of changing the column-labeling
behavior without modifying the innards of the backend; the column names
you see in psql are all the info there is on the client side.

I dunno whether it would be a good idea to change the backend's column
labeling rules for this case or not.  I'd be worried about breaking
existing applications that depend on the current labeling rules...

			regards, tom lane