Hi there,
not sure who is responsible for this issue. But anyway it's worth to check out.
http://social.msdn.microsoft.com/Forums ... 46a3acfb6d
$expand is broken in WCF DataServices 5 RTM with DevArt?
Please put the following line in the constructor of your context (the Devart.Data.Oracle.Entity.OracleEntityProviderServices class is defined in the %ProgramFiles%\Devart\dotConnect\Oracle\Entity\EF4\Devart.Data.Oracle.Entity.dll assembly):
Refer to http://blogs.planetsoftware.com.au/paul ... d-wcf.aspx . This is actually the problem of WCF Data Services which doesn't take into account the peculiarities of other RDMS (Oracle treats empty strings in varchar columns as null).
Code: Select all
Devart.Data.Oracle.Entity.OracleEntityProviderServices.HandleNullStringsAsEmptyStrings = true;
With this option active, we got WCF DataServices 5 working. However, most of our code is now broken, because all checks for null strings are now invalid (since empty strings are returned now instead of nulls).
It is possible to fix this properly? I mean, don't roundtrip constant to RDBMS for entity materialization sake?
It is possible to fix this properly? I mean, don't roundtrip constant to RDBMS for entity materialization sake?
The problem is fixed in WCF Data Services 5.1.0 (no need to use our workaround with this version). An upgrade is a recommended way of coping with it.
We considered not to fix the issue on our side for previous versions of WCF Data Services because this requires an architectural changes in the provider (time and resource consuming task).
We considered not to fix the issue on our side for previous versions of WCF Data Services because this requires an architectural changes in the provider (time and resource consuming task).