Devart Forums

Andrey,

So you are suggesting to execute multiple queries to get the desired result (typed nulls on/off)? In my opinion that's just working around the problem.

Can you give me a hint why the exceptions occur?
I can't see why the provider should behave different from the Ms Sql one.

And a final question: This is not considered a bug?
If this can't be resolved, I'll just have to workaround the problem as long as we're using EF + Oracle!

Peter

AndreyR wrote:This problem is associated with the fact that we have changed the behaviour associated with
typed Nulls in Oracle. The change was caused by the Charset mismatch problems in some situations.
To fix the issue you should set Devart.Data.Oracle.Entity.OracleEntityProviderServices.TypedNulls
to true before the query is executed.

Andrey,

I still have one of the mentioned problems.. with build 5.25.44 I encounter a ORA-1790, using typednulls=true is setting me back to the "Charset mismatch" ORA-12704 error. (like I had with older versions).

(fyi: the error occurs when having more than 1 one-to-many includes. Multiple many-to-one or one-to-one associations do not raise exceptions)

Do you already have a solution for this problem?
Loading references by hand as mentioned by Tom Wilkinson is not the correct way to solve this. As a workaround this is ok, but I really need the includes to work.

Peter