2010/3/11 Gábor Török <tgabo...@gmail.com>: > Hi! > > I'm using a database creation script file that is in UTF8 encoding, > and using "SET NAMES UTF8" it executes well with isql.exe. > I didn't want to ship isql.exe with my product, so I switched to using > Isql.FbBatchExecution. > The script executes, but the string "fejlesztő", when inserted into an > UTF8 encoded column, becomes "fejleszto". I read the script to a > string as UTF8, it reads correctly and "fejlesztő" remains "fejlesztő" > in the string (but it isn't UTF8 any more). I used UTF8 in the > connection string and the default charset of the database is > ISO8859_1. What connection character set and method should I use, to > execute SQL statements contained in C# strings to preserve non-ASCII > characters? > I investigated where do the information loss happen. I think it happens when the FesStatement (I work with embedded server at the moment) is prepared in FesStatement.cs, line 289, provider version 2.5.2, because the command text is converted to the database default charset. How can I execute statements that contain strings that can't be represented using the database default charset? Is it possible somehow? How does Isql.exe execute these comands producing the right result using the same database?
Gabor Torok ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider