What is so costly and not maintainable about passing xml (possibly bound to a schema)?
On Wed, Jul 14, 2010 at 9:54 AM, <[email protected]> wrote: > Just prepare the procedure and call it repeatedly without closing or removing > the command object. Passing a load of values as an xml or as a delimited > parameter is costly and not maintainable. > > Davy > ------Original Message------ > From: [email protected] > Sender: [email protected] > To: [email protected] > ReplyTo: ozDotNet > Subject: Batching ids for submitting to a stored proc > Sent: 14 Jul 2010 01:18 > > Hi all, > > I have a scenario as follows. I'm interested to hear what other people do to > solve this problem. > > I have two Checkbox Lists. The left Checkbox list is Customers. The right > Checkbox list is Shops. > On clicking the checkboxes in the left Customers Checkbox list, it posts back > and calls a stored > proc that retrieves the shops for displaying in the right Shops Checkbox list. > > Obviously there can be multiple checkboxes checked, and so a list of customer > ids somehow needs > to be passed into the stored proc. We are using LINQ to SQL. > > The question is, what do other people do in this situation? How would you get > the batch of ids into > the stored procedure for retrieving the list of shops? > > Regards, > Tony > > > > > > BBM pin:2589AEE0
