How to delete and insert records with the same primary key using Linq transactions?
We recommend you to open the transaction yourself and commit it, when necessary In this case the inernal transaction will not be opened t = db.Connection. BeginTransaction(); db. Transaction = t; DeleteOnSubmit(); SubmitChanges(); InsertOnSubmit(); SubmitChanges(); t.Commit().
We recommend you to open the transaction yourself and commit it, when necessary. In this case the inernal transaction will not be opened. T = db.Connection.
BeginTransaction(); db. Transaction = t; DeleteOnSubmit(); SubmitChanges(); InsertOnSubmit(); SubmitChanges(); t.Commit().
Each div has a pixel width, height, top, and left saved as individual records in the table. It has a primary key. We load all divs from the table to the web page, the user rearranges the squres, then in a single transaction saves the altered squares back to the table using Linq "OnSubmit" methods.
Our problem is we delete all the squares then reinsert all squares. Without transactions, this works fine. With transactions, it flags all records to be deleted, then the inserts actually update the records already flagged to be deleted.
In the end, some of the squares are missing. We do DeleteOnSubmit(), then InsertOnSubmit(), then eventually .SubmitChanges(). Where are we making our mistake?
How to you handle deleting and reinserting all in the same transaction? Obviously we could SubmitChanges() after the delete, but this wouldn't put it in the same transaction. Do you need the actual source code to continue?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
Delete and insert with same primary key in place of update?
SQL: To primary key or not to primary key?
LINQ to SQL insert primary key index?
Auto-increment a primary key in the LINQ to SQL DataContext “Insert” partial method?
How To Insert PK (Primary Key) in Table1 To FK(Foreign Key) in Table2 then show it the result?
Composite primary key and unique key as a foreign key?