Menu
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?
402
Using the Easy Connect Naming Method (aka EZ Connect) The easy connect naming method enables clients to connect to a database without any configuration. Data Source=username/password@//myserver:1521/my.service.com; Port 1521 is used if no port number is specified in the connection string.
A sid is the Site Identifier. It, plus the oracle_home, uniquely identify a database instance on a single machine. If you are on the machine with the database, you only need the oracle_sid and oracle_home to get connected directly.
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.
180
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
