Re: 7.1beta1 JDBC Nested cursor problem - Mailing list pgsql-bugs

From peter@retep.org.uk
Subject Re: 7.1beta1 JDBC Nested cursor problem
Date
Msg-id 976548205.3a34f16d2e3e2@webmail.retep.org.uk
Whole thread Raw
In response to 7.1beta1 JDBC Nested cursor problem  (Stu Coates <stu_coates@mail.com>)
List pgsql-bugs
Quoting Stu Coates <stu_coates@mail.com>:

> I think that I've found a little bug in the 7.1beta1 JDBC drivers.
> Attached is a simple test case which produces the problem on my setup
> (LinuxPPC 2000, on Apple PowerMac G3-400Mhz, 512MB).  It would seem that
> the drivers and/or the DBMS has a problem with nested queries, even
> simple ones.
>
> Here's the stacktrace:
>
> Bad Long
>   at org.postgresql.jdbc2.ResultSet.getLong(ResultSet.java:284)
>   at Test.go(Test.java:35)
>   at Test.main(Test.java:15)
>
> I'm using the 7.0.2 JDBC drivers against the 7.1beta1 backend and
> everything seems to be working fine with those, just the new ones
> (7.1beta1) have this problem.

Yes, I'm still tracing this one. I discovered it a few weeks ago while looking
at rewriting the standard queries in DatabaseMetaData, but the backend seems to
return not an Int/Long but the type name instead.

It's interesting to see that other code is getting the same problem.

Peter

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Can't use NULL in IN conditional?
Next
From: "Robert B. Easter"
Date:
Subject: Re: Can't use NULL in IN conditional?