From: Peter J. <pet...@gm...> - 2003-11-14 08:10:40
|
Hi Carlos, All, Please apologize, both for disturbing the thread structure by replying to the digest, and for giving my half-informed view. <car...@te...> wrote: > It's working fine for me, here is my test database: [...] > string connectionString = > @"Database=D:\TEST.GDB;" + > "User=SYSDBA;" + > "Password=masterkey;" + > "Server=localhost;" + > "Port=3050;" + > "Dialect=3;" + > "Charset=UNICODE_FSS;" + > "pooling=false;" + > "Role=;"; [...] > string sql = "insert into \"test\" (\"unicode_fss\", \"win1251\") values > (@unicodeValue, @win1251)"; > FbCommand unicode_insert = new FbCommand(sql, connection, transaction); > unicode_insert.Parameters.Add("@unicodeValue", FbDbType.VarChar).Value = > "áéíóú"; > unicode_insert.Parameters.Add("@win1251", FbDbType.VarChar).Value = > "áéíóú"; > unicode_insert.ExecuteNonQuery(); I'm the I18n guy, but I have near no experience with the .NET data provider. So the best I can say, is that this looks conceptually wrong to me. By specifiying a connection character set, using other interfaces, you specify in which character set the data is exchanged with server. From this point on, you are shielded from the actual different character sets used in different columns. Either I'm confused on this point, or the .NET provider behaviour is strange. Best Regards, Peter Jacobi -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |