' Optimistic concurrency' exception on bool fields
Posted: Fri 20 Mar 2015 11:46
Hi,
we have an 'optimistic concurrency' issue with version 8.4 of dotConnect for Oracle on entity fields of type bool. This issue does not occur with version 7.1.
Case:
- Tools/frameworks: Visual Studio 2013 Update 4, .NET FW 4.5/EDMX 3.0, Devart 8.4.215.0, Entity Framework 5 (code generation strategy 'Legacy ObjectContext'), Oracle 11g2.
- A table with a IS_TRUE NUMBER(1,0) column that is mapped on a bool property. The entity inherits EntityObject (legacy).
- The Concurrency Mode on that column is 'Fixed'.
- When updating an entity that has IS_TRUE = 1 as old value AND as new value, an 'OptimisticConcurrencyException' is thrown.
- The DBMonitor shows that the old value is 0 (this should be 1).
If necessary I can provide a VS2013 solution that reproduces the case.
Is this a bug?
greetings,
David
we have an 'optimistic concurrency' issue with version 8.4 of dotConnect for Oracle on entity fields of type bool. This issue does not occur with version 7.1.
Case:
- Tools/frameworks: Visual Studio 2013 Update 4, .NET FW 4.5/EDMX 3.0, Devart 8.4.215.0, Entity Framework 5 (code generation strategy 'Legacy ObjectContext'), Oracle 11g2.
- A table with a IS_TRUE NUMBER(1,0) column that is mapped on a bool property. The entity inherits EntityObject (legacy).
- The Concurrency Mode on that column is 'Fixed'.
- When updating an entity that has IS_TRUE = 1 as old value AND as new value, an 'OptimisticConcurrencyException' is thrown.
- The DBMonitor shows that the old value is 0 (this should be 1).
If necessary I can provide a VS2013 solution that reproduces the case.
Is this a bug?
greetings,
David