Linq to SQL EntitySet Records causing duplicate insertion

Posted by Savvas Sopiadis on Stack Overflow See other posts from Stack Overflow or by Savvas Sopiadis
Published on 2009-12-18T10:11:53Z Indexed on 2010/06/17 19:03 UTC
Read the original article Hit count: 296

Filed under:

linq-to-sql

In a WPF application i'm using Linq to SQL in a multi tier application.

(This is an archailogy photo filing application), so every excavation has its corresponding Pictures, thus a one-to-many relationship. This relationship is correctly created by SQLMetal (which i'm using to create the POCOs).

So here is the situation i 'm having trouble with:

Saving changes (either of new or altered objects) is done through UnitOfWork() pattern this way:

using (IUnitOfWork unitOfWork = UnitOfWork.Begin())
                {
    	 //if this is a new record
                    if (SelectedExcavation.excavation.ExcavationId == 0)
                    {
                        IsNewRecord = true;
                        excavService.Add(SelectedExcavation.excavation);
                    }

                    //send the actual changes to the dbms
                    unitOfWork.Commit();
               }

Everything works fine!

BUTTTT!!!

Whenever a record gets updated which has (already at least one ) corresponding Picture Record:

1) a new Excavation Record is inserted

2) the current Excavation Record gets updated

3) the previous Picture Record gets its Id changed to the newly created ExcavationId

What is going on under the hood? Does Linq to SQL not handle such simple update scenarios?

Thanks in advance

Related posts about linq-to-sql

how can i page my linq to sql result set

as seen on Stack Overflow - Search for 'Stack Overflow'
Remembering MySQL could use the instruction "limit" to indicate where I was starting my result set and how many wanted to have included. Select * FROM Users Limit [start], [Length] How can I do this in LinqToSql >>> More
LINQ to SQL and missing Many to Many EntityRefs

as seen on West-Wind - Search for 'West-Wind'
Ran into an odd behavior today with a many to many mapping of one of my tables in LINQ to SQL. Many to many mappings aren’t transparent in LINQ to SQL and it maps the link table the same way the SQL schema has it when creating one. In other words LINQ to SQL isn’t smart about many to many mappings… >>> More
Comparing LINQ to SQL vs the classic SqlCommand

as seen on Dot net Slackers - Search for 'Dot net Slackers'
tweetmeme_url = 'http://alpascual.com/blog/comparing-linq-to-sql-vs-the-classic-sqlcommand/';tweetmeme_source = 'alpascual';When you are coming from using SqlCommand and SqlConnection is difficult to move to another library for your database needs. For those people still in the limbo to make the decision… >>> More
Comparing LINQ to SQL vs the classic SqlCommand

as seen on Dot net Slackers - Search for 'Dot net Slackers'
tweetmeme_url = 'http://alpascual.com/blog/comparing-linq-to-sql-vs-the-classic-sqlcommand/';tweetmeme_source = 'alpascual';When you are coming from using SqlCommand and SqlConnection is difficult to move to another library for your database needs. For those people still in the limbo to make the decision… >>> More
LINQ to SQL Profiler

as seen on Dot net Slackers - Search for 'Dot net Slackers'
In this article we will be taking a look at the new LINQ to SQL Profiler from HibernatingRhinos. This tool gives you a view into the goings on of LINQ to SQL. Not only does it allow you to see the SQL that is generated by your LINQ queries but it also shows you information about your connections… >>> More

Developer IT