Hi
While passing parameters to a stored procedure in .Net code, why is it
important to pass them in the same order as defined in the stored
procedure? Cannot the driver determine the correct order based on the
schema and the parameter names supplied?
Also, any parameter name is accepted as a valid name. This behaviour
seems consistent with the driver expecting the order to be correct
rather than the parameter names to be correct.
My question is: Is there any way in which I can stop worrying about the
order in which the parameters are defined and simply add all the
parameters with the correct names as in the schema via the Firebird.Net
provider?
Of course, all the above information could be completely wrong as it is
based on my limited knowledge of the Firebird database and the
Firebird.Net provider.
Shreekar Joshi
KPIT Cummins Infosystems Ltd.| Ph: +91 020 6652 5000 extn. 2001
http://www.kpitcummins.com <http://www.kpitcummins.com>
Disclaimer: This message contains information that may be privileged or
confidential and is the property of KPIT Cummins. It is intended only
for the person to whom it is addressed. If you are not the intended
recipient, you are not authorized to read, print, retain copy,
disseminate, distribute, or use this message or any part thereof. If you
receive this message in error, please notify the sender immediately and
delete all copies of this message. KPIT Cummins does not accept any
liability for virus infected mails.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
