Hmmm, it should test using isNull() before trying to parse the object
type. I'll check.
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.
From: Gunnar R|nning [mailto:gunnar(at)candleweb(dot)no]
Sent: Tuesday, May 23, 2000 2:48 PM
Subject: [INTERFACES] JDBC 7.0 - ResultSet.getObject() bug
I just discovered what I think must be regarded as bug in the JDBC
shipped with the 7.0 release.
The JDBC spec states that ResultSet.getObject() should return "null" if
there is an SQL NULL value in the column. The JDBC driver for postgres
however in this case return an object, eg. in the case of an int value
returns an Integer object with the value of "0".
From looking at source code it is apparent that the problem is that the
getObject() method reuses the public getInt() methods with friends.
pgsql-interfaces by date
|Next:||From: Gunnar R|nning||Date: 2000-05-24 11:26:00|
|Subject: JDBC escape processing|
|Previous:||From: Gunnar R|nning||Date: 2000-05-23 13:53:49|
|Subject: JDBC 7.0 - PreparedStatement.setObject() bug.|