Andrus Adamchik wrote:
>
> "-1" means precision not specified (there was no better way to express it
> with primitive int). I'd say we should fix "-1" handling AbstractType. If
> precision is < 0, we should consistently call
>
> PreparedStatement.setObject(int, Object x, int)
>
> instead of
>
> PreparedStatement.setObject(int, Object x, int, int)
>
> We should probably file a bug for that.
I fixed it already - this does not seem to break anything (ran against all
my DBs here) and removes almost all outstanding test failures for DB2. The
few remaining failures are related to CHAR trimming. Looks like an easy
catch! :-)
Holger
This archive was generated by hypermail 2.0.0 : Thu May 22 2003 - 11:50:30 EDT