Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a list of values that I am looping through, determining whether each item exists in database table and then either updating or creating new row. Each time I use dataconext.submitchanges. I also need the ID for the newly created row which i get after submitchanges. Is there a better wa to do this than to connect on each cycle?
dont SubmitChanges for each record (iteration of the loop). make changes to the collections from your datacontext and SubmitChanges at the end. LINQ will look after the initial querying and the submitting at the end. you’re concurrency might be a problem but ignore that for now. likely, its not a concern unless ur iterating 1000’s of records.