+1 i suppose.

Same issue occurs with oracle 11g drivers as well, but you're correct, it's
not a regression -- I hadn't really noticed it because bizzarely, i'm using
the data direct drivers and they don't show the issue.

The issue's been raised on oracles forums a couple of times.

My kingdom for a typed null.

-shrug-


On Mon, Apr 13, 2009 at 2:20 AM, Dan Fabulich <d...@fabulich.com> wrote:

> Took me a few weeks, but I finally got around to installing a free instance
> of Oracle (Express Edition 10.2) and testing the null handling code we
> introduced in DbUtils 1.2 (DBUTILS-31).
>
> Sure enough, there's a bug, DBUTILS-55, but I don't think it's very
> important, since it's not a regression; it was there in DbUtils 1.1 and
> nobody appears to have noticed or cared.  :-)  Also, I have no idea how we
> could possibly fix it, since Oracle's JDBC driver doesn't support
> ParameterMetaData.getParameterType.
>
> With that done, and having tested successfully with Apache Derby, I'm now
> prepared to give RC3 my +1.  I believe we also already have a +1 from Joerg
> Schaible, so we still need two more binding +1s to release.
>
> -Dan
>
>
> Dan Fabulich wrote:
>
>
>> My third attempt at releasing a commons project; please test rigorously!
>>
>> RC3 includes an API change to QueryRunner to guarantee thread-safety.
>> (DBUTILS-52)
>>
>> NOTE: No one has yet explicitly said on-list that they have tested DbUtils
>> 1.2 with a real database.  We should not release it until somebody tries it
>> out with a real live Oracle database, as described below.
>>
>> Compatibility warnings:
>>
>> * API change in QueryRunner: the setDataSource method was removed in order
>> to fix a thread-safety bug (DBUTILS-52)
>> * We upgraded the JVM dependency from JDK 1.3 to JDK 1.4 (DBUTILS-31)
>> * Users who may have extended BeanListHandler.handleRow will find that
>> this method no longer exists (is no longer called) in DbUtils 1.2
>> (DBUTILS-37)
>> * Users who may have extended KeyedHandler will find that its protected
>> members are now final (to guarantee thread safety). (DBUTILS-51)
>>
>> PLEASE TEST THIS RELEASE WITH A REAL DATABASE!
>>
>> Although this project has reasonable unit tests, it has no integration
>> tests with any actual databases; it is quite possible that the fix for
>> DBUTILS-31 has broken something on Oracle, MS SQL Server, Derby, or your
>> favorite database.
>>
>> To verify DBUTILS-31, use QueryRunner to put a null value in a field, e.g.
>> with QueryRunner.update.  Ideally it would be good to verify putting nulls
>> in fields of various types: char, varchar, int, boolean, date, etc.
>>
>> --
>>
>> Tag:
>>
>> https://svn.apache.org/repos/asf/commons/proper/dbutils/tags/DBUTILS_1_2
>>
>> Site:
>>
>> http://people.apache.org/builds/commons/dbutils/1.2/RC3/site/index.html
>>
>> Binaries:
>>
>>
>> http://people.apache.org/builds/commons/dbutils/1.2/RC3/staged/commons-dbutils/commons-dbutils/1.2/
>>
>> [ ] +1 release it
>> [ ] +0 go ahead I don't care
>> [ ] -1 no, do not release it because
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Reply via email to