Yes, please add the issue to JIRA. Roberto
On Tue, April 26, 2005 12:31, Ron Grabowski said: > --- Maxime Levesque <[EMAIL PROTECTED]> wrote: >> 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 ) ? > > Keep in mind that this is still a 1.x release. Its not possible to test > every combination of .Net connection drivers. I'm sure more will be > added to the test suite as time goes on. > > If the provider exhibits strange behaviour (I saw a comment in the > source code about the MySql provider not supporting the CommandTimeOut > property) then IBatisNet can only do so much. Deep down, IBatisNet just > calls members of the System.Data interface. > >>From glancing at the providers.config file, I see 8 providers. If > everything is working fine for all of those providers and some new > provider is exhibiting strange behaviour I would say there's something > wrong with the provider. Perhaps you could spend some of the time saved > from using IBatisNet to port the test cases to your Oracle provider. > > I can understand your frustration with things not working. There only > seems to be two people using IBatisNet and Access (myself and another > lurker on the list). I've been able to track down the issues I was > having and they have since been corrected in the latest version in > source control. > > You should report this in the issue tracker: > > http://issues.apache.org/jira/browse/IBATISNET > > Perhaps another attribute could be added to the <provider> > node...something along the lines of: > > setParameterSizeIfNotDbString="false" > > That might fix issues with future providers as well. >
