DevForce Community Forum : Concurrency column in a Complex Object

DevForce Community Forum : Concurrency column in a Complex Object http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2010 : Concurrency column in a Complex Object Mon, 13 Apr 2026 17:18:47 -700 Fri, 20 May 2011 11:03:30 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=2698 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Concurrency column in a Complex Object : Yeah.Sorry Dan, I went through... http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10770#10770 Author: robertg
Subject: 2698
Posted: 20-May-2011 at 11:03am

Yeah. Sorry Dan, I went through a number of permutations in both DF and EF trying to get it to work before I broke the bad news that it doesn't. I really hope EF documentation is improved significantly soon.]]> Fri, 20 May 2011 11:03:30 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10770#10770 Concurrency column in a Complex Object : I was afraid of that. Oh, well,... http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10767#10767 Author: danielp37
Subject: 2698
Posted: 20-May-2011 at 7:33am

I was afraid of that. Oh, well, it would have been really convenient. I have just gone with removing the ModifiedAt from the ComplexObject and putting it as a regular scalar property on the Entity itself and this appears to be working.]]> Fri, 20 May 2011 07:33:18 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10767#10767 Concurrency column in a Complex Object : Dan, This limitation seems... http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10763#10763 Author: robertg
Subject: 2698
Posted: 19-May-2011 at 5:23pm

Dan,

This limitation seems to be with EF itself, as a project in plain EF shows the same behavior as one with DF. For now, I suggest that you check concurrency against simple scalar properties instead, as that definitely works.

-- Robert

]]> Thu, 19 May 2011 17:23:28 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10763#10763 Concurrency column in a Complex Object : Dan, We should be support... http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10758#10758 Author: robertg
Subject: 2698
Posted: 19-May-2011 at 2:42pm

Dan,

We should be support the functionality as EF, in this. I'll research this, and get back to you tomorrow.

Thanks,

-- Robert

Edited by robertg - 19-May-2011 at 4:39pm]]> Thu, 19 May 2011 14:42:43 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10758#10758 Concurrency column in a Complex Object : I have a complex object called... http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10757#10757 Author: danielp37
Subject: 2698
Posted: 19-May-2011 at 1:02pm

I have a complex object called "AuditInfo" that basically has 4 properties on it: CreatedAt, CreatedBy, ModifiedAt, ModifiedBy.

I am trying to set the ModifiedAt as a AutoDateTime concurrency column.

When I set the Concurrency Stategy to AutoDateTime, I am able to save the object, but the update doesn't update the ModifiedAt to the current DateTime.

When I set the Concurrency Stategy to Client and set the property during the EntityServerSaveInterceptor.ExecuteSave method, the update statement sets the ModifiedAt field, but it also checks the ModifiedAt column against the new value of ModifiedAt instead of the original value.

Am I doing something wrong or are concurrency fields on complex objects not supported?

If I could even have the whole AuditInfo complex type treated as a concurrency property then I could use that but when I set the Concurrency Mode to Fixed on that Property of the Entity it doesn't appear to be checking it for concurrency.

Dan

]]> Thu, 19 May 2011 13:02:59 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2698&PID=10757#10757