Comments on: Linq to SQL Quirks Part 4: Circular References http://rainstorms.me.uk/blog/2009/07/10/linq-to-sql-quirks-part-4-circular-references/ Problems that I come across in day to day coding Tue, 30 Aug 2011 06:31:50 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Slavik http://rainstorms.me.uk/blog/2009/07/10/linq-to-sql-quirks-part-4-circular-references/comment-page-1/#comment-15482 Slavik Wed, 02 Feb 2011 14:06:04 +0000 http://rainstorms.me.uk/blog/?p=239#comment-15482 My version: db.ResourceVersions.InsertOnSubmit(newResourceVersion); db.SubmitChanges(); newResource.LastVersion = newResourceVersion; db.SubmitChanges(); ts.Complete(); My version:
db.ResourceVersions.InsertOnSubmit(newResourceVersion);
db.SubmitChanges();

newResource.LastVersion = newResourceVersion;
db.SubmitChanges();

ts.Complete();

]]> By: wizzard http://rainstorms.me.uk/blog/2009/07/10/linq-to-sql-quirks-part-4-circular-references/comment-page-1/#comment-5359 wizzard Mon, 16 Nov 2009 09:22:40 +0000 http://rainstorms.me.uk/blog/?p=239#comment-5359 Ideally, yes, and if you can work out a way to do it in a single transaction, that would be better. However, I was really just focusing on the problem and a workaround. It isn't a perfect workaround, but the risk of failure between the 2 transactions is fairly small, and in the case of the system that I was working on, the consequences are not so severe. Ideally, yes, and if you can work out a way to do it in a single transaction, that would be better. However, I was really just focusing on the problem and a workaround. It isn’t a perfect workaround, but the risk of failure between the 2 transactions is fairly small, and in the case of the system that I was working on, the consequences are not so severe.

]]> By: Adriano http://rainstorms.me.uk/blog/2009/07/10/linq-to-sql-quirks-part-4-circular-references/comment-page-1/#comment-5356 Adriano Fri, 13 Nov 2009 16:54:23 +0000 http://rainstorms.me.uk/blog/?p=239#comment-5356 Hi, You solved this problem by breaking the circular reference in two operations. But don't you need a transaction for these two operations? I mean, to treat these operation as one operation only? Thanks, Adriano Hi,

You solved this problem by breaking the circular reference in two operations. But don’t you need a transaction for these two operations? I mean, to treat these operation as one operation only?

Thanks,

Adriano

]]> By: wizzard http://rainstorms.me.uk/blog/2009/07/10/linq-to-sql-quirks-part-4-circular-references/comment-page-1/#comment-4240 wizzard Fri, 14 Aug 2009 08:17:22 +0000 http://rainstorms.me.uk/blog/?p=239#comment-4240 No – the reason it is a problem with inserts is that Linq to SQL doesn’t know which way around to insert the records because they both have IDs referencing each other and neither ID exists yet because they haven’t been inserted. With updates, the records already have IDs, so it just keeps those No – the reason it is a problem with inserts is that Linq to SQL doesn’t know which way around to insert the records because they both have IDs referencing each other and neither ID exists yet because they haven’t been inserted. With updates, the records already have IDs, so it just keeps those

]]> By: Wes http://rainstorms.me.uk/blog/2009/07/10/linq-to-sql-quirks-part-4-circular-references/comment-page-1/#comment-4233 Wes Thu, 13 Aug 2009 21:24:22 +0000 http://rainstorms.me.uk/blog/?p=239#comment-4233 Thank you, that solved the issue for me today with inserting. Does the same issue ever come up with updates? Thank you, that solved the issue for me today with inserting.

Does the same issue ever come up with updates?

]]>