Dec 17, 2014 at 7:11 PM
I've run a simple test and the results suggest concurrency checking is not implemented. Would you verify the current state of concurrency checking for me and if there is plan for implementation?

When I use the term concurrency checking, I'm referring to a use case involving two users, unknowingly, editing the same field of the same record. User A changes and saves over the original value. User B then changes and saves over what they believe to be the original value, but instead has just over written User A's change.
Dec 20, 2014 at 1:57 AM
You can handle this with RowVersion from SQL and EF, this is something you can easily add (framework with EF provider is currently 12 total classes). We will add this to our back log and ship the next release with it.
Marked as answer by lelong37 on 12/19/2014 at 5:57 PM