Re: Best practice
- From: "Marina" <someone@xxxxxxxxxx>
- Date: Fri, 13 May 2005 15:48:42 -0400
If that object has no method to set all of them, then there is nothing you
can do.
I honestly don't think you are going to see an actual performance problem by
having to set 9 properties instead of calling 1 method.
"Diffident" <Diffident@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9CD93E76-493A-408F-AE37-604D18C0CB35@xxxxxxxxxxxxxxxx
> Hello All,
>
> Best coding strategies for calling stored procedures from ASP.NET. As you
> are all aware that accessing a property is expensive than calling a
> method.
> For example in order to call a stored procedure which accepts 2 input
> parameters, we are currently following the below standard to set a single
> parameter:
>
> objOracleParameterSTATUS = new System.Data.OracleClient.OracleParameter
> ();
> objOracleParameterSTATUS.ParameterName ="STATUS_IN";
> objOracleParameterSTATUS.SourceColumn = "STATUS";
> objOracleParameterSTATUS.OracleType=System.Data.OracleClient.OracleType.Number;
> objOracleParameterSTATUS.Size =1;
> objOracleParameterSTATUS.Precision =0;
> objOracleParameterSTATUS.Scale =0;
> objOracleParameterSTATUS.Direction = System.Data.ParameterDirection.Input;
> objOracleParameterSTATUS.SourceVersion=System.Data.DataRowVersion.Current;
> objOracleParameterSTATUS.Value =STATUS;
> bjOracleCommand.Parameters.Add (objOracleParameterSTATUS);
>
> So on the whole we are setting 9 properties for a single parameter and if
> this stored procedure accepts 10 parameters, then this process has to be
> repeated for those many parameters.
>
> Can any of the solution developers suggest me an alternative choice for
> the
> above code or how can I make this less expensive and efficient.
>
> Thanks for your help!!!
.
- References:
- Best practice
- From: Diffident
- Best practice
- Prev by Date: Re: Search with drop down list
- Next by Date: Re: SQLDataAdapter fails
- Previous by thread: Best practice
- Next by thread: Re: Best practice
- Index(es):
Relevant Pages
|