Unicode Option for Oracle ConnectionString

Why does Oracle ODP not recognize Unicode = true and what does the Devart Provider do?

When I have data containing the string: "ñãõ, éóúý", my asp.net application shows "???, ????" if I use Oracle ODP. When I try to put the attribute Unicode=truein the connection string, it says that this is an invalid attribute.

The same behavior can be reproduced using the Devart provider. But it happens that when I put the attribute Unicode=truein the connection string, everything is well displayed on the screen of my asp.net application.

Why is this happening? What attribute could I use in the Oracle Data Provider (Oracle.DataAccess.Client) so that my characters are displayed the way I want?

+5
source share
1 answer

ODP.NET always supports Unicode , reports this link:

http://www.oracle.com/technetwork/topics/dotnet/code-154692.html

There is no need to use UNICODE in the connection string. In fact, this attribute must be removed.

Perhaps if the string is incorrect, then ODP.Net is not the fault.

Thanks @Vache for your comment.

0
source

All Articles