I found a short blog comment talking about some other strange behaviors providers exhibit:
http://weblogs.asp.net/pwilson/archive/2004/01/09/49174.aspx#49405 --- Roberto R <[EMAIL PROTECTED]> wrote: > Yes, specifying the size works. However, I think Maxime was looking > for a > solution where a size in a parameterMap is not required (since > dynamic SQL > and inline parameter won't run with ODP if a size is required...the > size > issue and those other related issues with ODP.NET <http://ODP.NET> > and the > DataMapper were covered a few months ago on this list). > > Maxime, it would be a big help if you could try the lastest code from > SVN > with the ODP provider to see if the changes help (the NUnit ODP maps > were > also modified last week based on the changes). > > Thanks! > > Roberto > > > On 5/2/05, Ron Grabowski <[EMAIL PROTECTED]> wrote: > > > > > > and thought of another possible solution using parameterMaps. He > should > > be able to use a parameterMap to specfy the size, precision, and > scale > > of the Varchar2 parameters that are causing him trouble: > > > > >
