Hi,
I've noticed that when I call stored proc, its parameters must be in exactly same order as they are defined in the Oracle. This was not the case for Microsoft implementation of Oracle data provider for .Net.
So my question is there any way to make dotConnect to ignore the order of stored proc parameters? We've got a big legacy project with a lot of stored proc calls. It's a bit painful for us to check parameters order for each one of them.
Stored procedure input parameters ordering
Please refer to the Using Parameters article in our online documentation:
If parameters are added to the command collection in the order that is different from the function parameters order in database, it is necessary to describe the command by setting OracleCommand.ParameterCheck to true to reoder parameters in a proper way.
Please use the OracleCommand.PassParametersByName=true option (instead of OracleCommand.ParameterCheck=true). Also please send us a small test project with the corresponding DDL/DML script to reproduce the problem with ParameterCheck in our environment.
New version of dotConnect for Oracle 6.10 is released!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=20115 .
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=20115 .