db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Dudziak <tom...@gmail.com>
Subject Re: setObject(idx, bigDecimal, Types.NUMERIC); doesn't work ?
Date Fri, 06 Jan 2006 14:29:48 GMT
On 1/6/06, Lance J. Andersen <Lance.Andersen@sun.com> wrote:
>  The spec needs to be followed whether you agree or disagree with the
> semantics.  The javadocs are very specific here and there must have been a
> reason for this decision at the time.  As i indicated to Craig, I am trying
> to find out if any of the previous spec leads recall why this was done
> before i do anything else on this issue.
>
>  A change in this area could potentially break existing applications who are
> relying on the functionality as documented.  This would have to be weighed
> by the JDBC EG prior to any changes in behavior.
>
>  It is just not a simple change the javadocs at this time.  This has to be
> researched and discussed further.  It could well be that no one is impacted,
> i just do not know at this point in time.

Agreed. While my personal opinion is that this is not intuitive and
problematic at times (e.g. what to do if the value to be inserted into
a NUMERIC/DECIMAL is a double, not a BigDecimal ? Should the driver
clip the double to scale 0 ?) the spec stands as it is.

regards,
Tom

Mime
View raw message