From: | JohnDz <John_dzilvelis(at)valpak(dot)com> |
---|---|
To: | "pgsql-interfaces(at)postgreSQL(dot)org" <pgsql-interfaces(at)postgreSQL(dot)org> |
Cc: | Sebastian Meyer <meyer(at)mevis(dot)de> |
Subject: | Re: [INTERFACES] pgsql.tcl: Bug concerning joins |
Date: | 1998-09-01 17:15:56 |
Message-ID: | 35EC2BCC.2A3C0FD9@valpak.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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 |
-----------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre-Olivier Gaillard | 1998-09-01 17:20:51 | Jdbc and oid |
Previous Message | Peter T Mount | 1998-09-01 17:07:39 | Re: [INTERFACES] JDBC ResultSet Serializable ??? |