Quoting Stu Coates <stu_coates(at)mail(dot)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.
In response to
pgsql-novice by date
|Next:||From: Mike Hammonds||Date: 2000-12-11 17:53:18|
|Subject: default password|
|Previous:||From: chriswood||Date: 2000-12-11 14:24:28|
|Subject: subselect question|
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2000-12-11 15:51:56|
|Subject: Re: Can't use NULL in IN conditional? |
|Previous:||From: Kevin Gilpin||Date: 2000-12-11 14:51:35|
|Subject: CREATE FUNCTION distributors_id_max() RETURNS INT4
AS Bad Timestamp Format thrown by jdbc7.0-1.2.jar|