Serious Problem with dotConnect for Oracle
Posted: Thu 19 Nov 2015 11:07
Hi,
We encounter a serious problem with dotConnect for Oracle that happens randomly at customer's site and we cannot reproduce or send specific sample code.
We target Oracle 10g and the problem occurs with latest version 8.5.535 as well as the older version 84.313. We use Entity Framework 6.1.3
A simple projected column of Boolean type (NUMBER(1)) may get TRUE value (1) instead of FALSE (0) that is stored in the database!
It is a query of the following form:
SELECT ... , Table1.ID, Table1.Name, Table1.isActive , ...
WHERE ...
JOIN ...
LEFT JOIN...
In our scenario, it returns about 500 entities and each time the correctness varies: Most times all of them have correct values but some times around 120 of them have correct values, sometimes 134 of them have correct values etc.
Sometimes it works correctly, sometimes not! We cannot figure out the conditions that it provides wrong result. It is not a matter of concurrency on context, the context is local and immediately disposed afterwards.
We have a clue: we are pretty sure it did NOT happen in the last software version that we have been using Model-First (CSDL, MSL, SSDL) model. It appeared since the first day that we deployed a Code-First model.
Any help? Guideline? Somehow to output debug information that will help you understand the situation?
Thanks in advance
We encounter a serious problem with dotConnect for Oracle that happens randomly at customer's site and we cannot reproduce or send specific sample code.
We target Oracle 10g and the problem occurs with latest version 8.5.535 as well as the older version 84.313. We use Entity Framework 6.1.3
A simple projected column of Boolean type (NUMBER(1)) may get TRUE value (1) instead of FALSE (0) that is stored in the database!
It is a query of the following form:
SELECT ... , Table1.ID, Table1.Name, Table1.isActive , ...
WHERE ...
JOIN ...
LEFT JOIN...
In our scenario, it returns about 500 entities and each time the correctness varies: Most times all of them have correct values but some times around 120 of them have correct values, sometimes 134 of them have correct values etc.
Sometimes it works correctly, sometimes not! We cannot figure out the conditions that it provides wrong result. It is not a matter of concurrency on context, the context is local and immediately disposed afterwards.
We have a clue: we are pretty sure it did NOT happen in the last software version that we have been using Model-First (CSDL, MSL, SSDL) model. It appeared since the first day that we deployed a Code-First model.
Any help? Guideline? Somehow to output debug information that will help you understand the situation?
Thanks in advance