The latest source does do the setting of parameter size copy, and the test
suite does include the ODP.NET driver (there are 2 directories containing
maps for testing both the MS provider and ODP). :-)
But yes, it may seem that more folks are using the MS driver based on the
list traffic.
Roberto
On Tue, April 26, 2005 11:22, Maxime Levesque said:
>
> It was indeed a bug (at least with my definition of bug...)
>
> To recapitulate (again) : insertion of strings (as varchar2) end up as
> null
> in the DB.
>
> The Microsoft driver is not affected by this, but for us it is not an
> option
> (we need the extra
> features of the oracle driver).
>
> The fix involves a change in the class :
>
> IBatisNet.DataMapper.MappedStatements.MappedStatement
>
> // FIX BEGIN (line 225)
>
> if(typeof(command).FullName.Equals("Oracle.DataAccess.Client.OracleCommand")
> &&
> !sqlParameter.DbType.Equals(System.Data.DbType.String))
> ((IDbDataParameter)parameterCopy).Size
> ((IDbDataParameter)sqlParameter).Size;
> // END FIX
>
> A few non public fields of oracle's connection differ when
> IDbDataParameter.Size is set
>
> - Not good (when Size set to 0) :
> m_maxSize 0 int
> m_modified true bool
> m_precision 0 byte
>
> - Good (when Size set never set) :
> m_maxSize -1 int
> m_modified false bool
> m_precision 100 byte
>
>
> My conclusion is that no one else is using ibatis + oracle's odp.net
> together, and your test suite probably doesn't include the combination,
> Which leaves me a bit worried of using iBatis for our project.
>
> On the other hand, I like the fact that ibatis leaves full control
> of the sql/stored procs, but using an untested driver is risky
> (this is a commercial project).
>
> So, is this driver supported, or will it be in the very
> Near future ? (i.e. will the odp.net driver be
> Tested as part of the nunit test suite ) ?
>
