OK, so what should I do? 1] put back encoding of "UNICODE_FSS" to "UTF-8" and find replacements for DB client and ODBC driver. Currently I use IBExpert and ODBC "Firebird/Interbase Driver" by IBPhoenix.
2] keep the changed version and possibly have invalid unicode characters in my DB when using other ODBC driver than the one mentioned above. ""Jiri Cincura"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Changing to NONE does the same thing, that IBExpert do. Saving raw > UTF-8 date into column without any interpretation. So that you match > with IBEXpert. > > -- > Jiri {x2} Cincura (Microsoft Student Partner) > http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Firebird-net-provider mailing list > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
