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 |
-----------------------------------------------------------------