This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
AW: java.sql.ResultSet.getObject() Kawa(?) bug, (as <int> 1)
- From: "Hoehle, Joerg-Cyril" <Joerg-Cyril dot Hoehle at t-systems dot com>
- To: brl-users at lists dot sourceforge dot net, kawa at sources dot redhat dot com
- Date: Thu, 15 Aug 2002 12:21:30 +0200
- Subject: AW: java.sql.ResultSet.getObject() Kawa(?) bug, (as <int> 1)
Per Bothner wrote:
>Kawa should be able to figure out that getObject(int) is a closer
>match than getObject(String). I'm not sure what it doesn't.
>Could you try the latest CVS Kawa to see if the bug is still there?
Here are the results from using your kawa-1.6.99.1.jar (1359087 bytes) from beginning of August.
Entering (invoke rs 'getXYZ 1) at prompt
ok: getByte getShort getInt getString getBoolean getBytes getDate getTime
bad: getObject getLong getBigDecimal getDouble getFloat getTimestamp
bad means: java.sql.SQLException: Column not found
(i.e. findColumn in backtrace), not the old "Argument <2spaces>to
'...getInt' has wrong type", which seems gone now.
So what did you change? :-) How comes that the fix is partial?
Regards,
Jorg Hohle.