Unicode Parameter on Oracle Connectionstring
character-encoding, devart, odp.net, oracle
Solution
ODP.NET is always Unicode aware, says this link:
http://www.oracle.com/technetwork/topics/dotnet/code-154692.html
There is no need in using UNICODE in the connection string. In fact, this attribute should be removed.
Probably if the string is wrong ODP.Net is not the thing to blame.
Thanks @Vache for your comment.
Problem
Why does not Oracle ODP recognize the parameter Unicode=true and Devart's Provider does? WHen I have data containing the string : "ñãõ,éóúý" , my asp.net application shows "???,????" if I'm using Oracle's ODP. WHen I try to put the attribute `Unicode=true` in the connectionstring, it says that it's an invalid attribute. THe same behavior can be reproduced with Devart's provider. But it happens that when I place the `Unicode=true` attribute in the connectionstring everything is displayed nicely on the screen of my asp.net application. Why does that happen? Which attribute could I use in Oracle Data Provider (Oracle.DataAccess.Client) so that I can have my characters shown the way I want?