Page 1 of 1
Devart dotConnect for Oracle and Unicode
Posted: Tue 12 Jan 2016 14:14
by patrasch79
Hi guys!
It seems that Unicode characters don't work anymore. e.g. German ä, ü, ö....
I have Version 8.5.492.0 und just see ? in my NVARCHAR2 strings instead of ä, ö, ö...
It seems to work if i set Unicode=true on my connection.
Did the behavior change?
I'm sure it worked in a previous version without setting Unicode=true.
Re: Devart dotConnect for Oracle and Unicode
Posted: Wed 13 Jan 2016 12:56
by Shalex
patrasch79 wrote:Did the behavior change?
Please look for "unicode" entries in
https://www.devart.com/dotconnect/oracl ... story.html.
If this doesn't explain the issue, please give us the following information:
1) are there any drawbacks of using "Unicode=true" in your project?
2) the exact build (x.x.x) of dotConnect for Oracle you used before
3) have you encountered the unicode behaviour change with a plain ADO.NET code or at Entity Framework level?
4) are you using OCI (via Oracle Client) or
Direct mode?
5) are there any other changes in your environment (.NET Framework
installed or used in the project, Oracle client version or its settings, the Entity Framework version used, etc)?
Re: Devart dotConnect for Oracle and Unicode
Posted: Wed 13 Jan 2016 13:23
by patrasch79
* i only have an Unicode Oracle Database right now, but what about Unicode=true and a non-Unicode Database (e.g. charset WE8MSWIN1252)? does it work? i can't test it right now.
* i used serveral dotConnect-Versions before e.g 8.3.135.0
* i use Entity Framework 6.1.3 Code First but the behavior is the same ExecuteNonQuery on OracleConnection
* i use OCI
* nothing changed except dotConnect version
i was just curious what changed, but i could use Unicode=true if it works on non-Unicode Database too.
Re: Devart dotConnect for Oracle and Unicode
Posted: Mon 18 Jan 2016 12:16
by Shalex
patrasch79 wrote:i was just curious what changed
There were several unicode fixes (see
https://www.devart.com/dotconnect/oracl ... story.html).
patrasch79 wrote:but i could use Unicode=true if it works on non-Unicode Database too
It should work. If you encounter any issue with "Unicode=true", please contact us.