Clean Domain Model With Entity Framework Concurrency Why Am I Forced To Use RowVersion?

Question

Hi have a domain model which is nice and clean. Such as:

public class Blog
{
    public int Id {get;set;}
    public string Title {get;set;}
    public string Body {gets;set;}
}

Why does Entity Framework force me to pollute the domain model with the RowVersion property to provide for concurrency?

My model doesn't want or need to know about this so why should I be forced to use it? Is there another way to perform concurrency checking? If so is it better/worse or faster/slower than adding a row version? Or can I add RowVersion somewhere else where it's not in the domain model. I'm using EF 4.1 with the fluent api.

Thanks

score 0 · Answer 1 · answered Jan 01 '13 at 14:28

0

Try to use a base class and put all properties for security, concurrency checking in there.

answered Jan 01 '13 at 14:28

phnkha

7,782
2
24
31

This will still pollute my domain model. Just in a different place. – big_tommy_7bb Jan 01 '13 at 14:29
But not too much, only a field in base class :-) – phnkha Jan 01 '13 at 14:33

Clean Domain Model With Entity Framework Concurrency Why Am I Forced To Use RowVersion?

1 Answers1