0

I have Linq-to-SQL and a stored procedure (with generated .dbml file and usp calling like a method) and .NET.

So:

public IEnumerable<usp_Orders_Process_SelectResult> usp_Orders_Process_Select()
{
    return _dataContext.usp_Orders_Process_Select();
}

This is execution of my stored procedure, but there are 5 arguments (Guid, int, date, date, int). Of course, I can change it like:

public IEnumerable<usp_Orders_Process_SelectResult> usp_Orders_Process_Select(Guid par1, int par2, date par3, date par4, int par5)
{
    return _dataContext.usp_Orders_Process_Select(par1, par2, par3, par4, par5);
}

But it's not very good.

Is there a way to organize list with SqlParameter, which I could then send into my usp? Thx.

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
FSou1
  • 1,861
  • 4
  • 18
  • 25
  • I don't think is bad, is actually very simple and exact and once you edit the stored procedure and refresh the model you will have one more parameter in there and a compile time error so you will not forget to add the missing parameter, same when you remove one. With the typeless approach of parameters list or collection, you would easily forget to add/remove them when things change. – Davide Piras Nov 16 '11 at 22:06
  • Seems okay to me as well, all passing in parameterlist does is move and obscure the issues with bad parameters. The more the compiler can find for you the better. – Tony Hopkinson Nov 16 '11 at 22:25

0 Answers0