>>>>>>>>>>>> Craig L Russell wrote (2006-01-05 16:59:00): > Hi, > > I asked Lance Anderson, spec lead for JDBC 4.0, about this issue and > he replied that he thinks that due to compatibility with existing > applications that rely on this behavior, it's unlikely to change. > > My opinion is that the behavior is surprising, and that most > applications that discover that the API with a BigDecimal parameter > truncates all the decimals, simply change to the API call that allows > you to specify the scale. > > So my big unfounded claim is that there is no use for the API without > the scale parameter taking a BigDecimal parameter with the current > behavior. And that changing it has low risk of untoward results.
Do you suggest that we should throw an exception if setObject without scale is called with a BigDecimal argument? Or do you suggest that we let setObject default to the scale of the BigDecimal parameter and thus violating the spec? Bernt -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway
pgp0KNmNQWVpq.pgp
Description: PGP signature
