Re: [Firebird-net-provider] Order of parameters to stored procedure

[Ivan A. <int...@da...>]

Hi,

Do you think introducing the overhead and processing time to determine the
parameter order is worth? I mean . getting the schema on each procedure call
and parsing it seems like "harder work" than just ordering the parameters at
design time.

A sort of a workaround you could use is inserting the parameters in a temp
table (where you call the columns by name) and executing the procedure with
no parameters (except maybe some ID). I know it doesn`t sound too graceful,
but it could be implemented overnight J

 

From: fir...@li...
[mailto:fir...@li...] On Behalf Of
Shreekar Joshi
Sent: Wednesday, November 14, 2007 11:38 AM
To: For users and developers of the Firebird .NET providers
Subject: [Firebird-net-provider] Order of parameters to stored procedure

 

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.