[Firebird-net-provider] Incorrect handling of UNICODE_FSS or UTF8 charset of connection during, accessing DB with charset NONE

Tue, 11 Dec 2007 04:09:42 -0800

We have DB with charset NONE on Firebird 2.0. Our web-application should support different languages so we establish connection to this DB with charset UNICODE_FSS. Old version of our tool use Firebird .Net Data Provider 1.7.1 for .NET 1.1 and it work correct. We tried to use Firebird .Net Data Provider 2.1.0 for .NET 2.0 to access same DB via connection with same settings from .NET 2.0 and we found that german umlauts and russian signs are saved into DB incorrectly.
We prepared test application to show this problem (source codes in zip-archive as attachment FBEncodingTest.archive). Application get data from textbox, putting it into DB, retrieve it back from DB and show in second textbox. Retrieved data is different to putted one. 

Input data used by us to illuminate problem:

1. DB Test with charset NONE on local Firebird 2.0 or last snapshot of 
Firebird 2.1;

2. Connection string:

Data Source=localhost;Port=3050;Database=Test;User 
Id=test;Password=test;Dialect=3;Max Pool Size=10;Charset=UNICODE_FSS;

3. Default input text is included in application.



Attachment:
FBEncodingTest.archive

Description: Binary data


-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider






















					Reply via email to