Received: from sunserv1.valpak.com (sunserv1.valpak.com [168.151.253.14]) by hub.org (8.8.8/8.7.5) with ESMTP id RAA11847 for ; Tue, 1 Sep 1998 17:13:16 -0400 (EDT) Received: from valpak.com ([172.16.1.76]) by sunserv1.valpak.com (Netscape Messaging Server 3.01) with ESMTP id AAA10808; Tue, 1 Sep 1998 17:12:54 -0400 Sender: "System Administrator" Message-ID: <35EC2BCC.2A3C0FD9@valpak.com> Date: Tue, 01 Sep 1998 17:15:56 +0000 From: JohnDz X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.1.24 ppc) MIME-Version: 1.0 To: "pgsql-interfaces@postgreSQL.org" CC: Sebastian Meyer Subject: Re: [INTERFACES] pgsql.tcl: Bug concerning joins References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sebastian Meyer wrote: > > I found a bug processing a simple join like > SELECT s1.b,s2.b FROM pgsqlbug1 s1, pgsqlbug2 s2 WHERE s1.a = s2.c; > This bug only occurs whern using pgsql.tcl. > > > Using pgsql.tcl from Tcl however I get: > > meyer> SELECT s1.b,s2.b FROM pgsqlbug1 s1, pgsqlbug2 s2 WHERE s1.a = s2.c; > > attributes: b b > lAttributes: {b 1042 -1} {b 1042 -1} > Tuple 0: {from table 2} {from table 2} > > ... what is wrong, obviously. > I can't figure out why this happens, but I did find a work around. Try: SELECT s1.b AS b1, s2.b AS b2 FROM pgsqlbug1 s1, pgsqlbug2 s2 WHERE s1.a = s2.c ; This worked fine with pgsql.tcl . By the way, I was able to duplicate your error using pgsql.tcl. I think it has to do with how proc pg_exec or pg_result processes columns with the same name ( .b ). -- ----------------------------------------------------------------- |John Dzilvelis | -----------------------------------------------------------------