Incorrect handling of UNICODE_FSS or UTF8 charset of connection during,
accessing DB with charset NONE
------------------------------------------------------------------------------------------------------
Key: DNET-145
URL: http://tracker.firebirdsql.org/browse/DNET-145
Project: .NET Data provider
Issue Type: Bug
Components: ADO.NET Provider
Affects Versions: 2.1.0
Environment: ASP.NET 2.0
Firebird 2.0.1 or Firebird 2.1
Reporter: Igor
Assignee: Carlos Guzman Alvarez
Priority: Critical
Connection with charset=UNICODE_FSS or UTF8 to database with charset=NONE.
Text with german umlauts was stored in DB via ADO.NET Provider 2.1. Later this
text was retrieved from DB and is different to stored one: special signs and
german umlauts are damaged. Same operations via ADO.NET Provider 1.7.1 give
correct results.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
