On Fri, Sep 29, 2006 at 02:22:44PM +0300, Alexander Vlasov wrote: > Package: libct3 > Version: 0.63-3
> Hello. > After upgrading freetds (libct3) to version 0.63-3 I faced one strange > but very serious problem. > All perl scripts using libdbd-sybase-perl now producing a warning about > encoding (like this): > Sybase.DatabaseError: Msg 2409, Level 11, State 2, Line 2 > Cannot find the requested character set in Syscharsets: name = > 'ANSI_X3.4-1968'. > Msg 2411, Level 10, State 1, Line 2 > No conversions will be done. > (ISO-8859-1 instead of ANSI_X3.4-1968 if script has been launched in > en_US locale instead of C/POSIX). This is a best guess at the character set based on the locale settings. The library doesn't have any built-in mapping of Unix charset names to the character set names that Sybase servers want (which are not standardized in any way). > (unofficial) python-sybase produces the same error and dying. > Seems Sybase ASE has "iso_1" as data encoding; adding "client charset = > iso_1" in /etc/freetds/freetds.conf or /etc/freetds/locales.conf desn't > help. The correct option is 'charset' rather than 'client charset'. E.g.: [en_US] char set = iso_1 I'll address this in a future upload of freetds by providing a default or example locales.conf file in the package. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
