Skip to Content.
Sympa Menu

freetds - Re: [freetds] unicode server data incorrectly converted to iso-8859-1 on client

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Daniel Fazekas <fdsubs AT t-online.hu>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] unicode server data incorrectly converted to iso-8859-1 on client
  • Date: Mon, 31 May 2010 15:33:04 +0200

On May 31, 2010, at 14:34, Razvan Cosma wrote:

> Hi - you're right, setting utf-8 in [global] gets rid of the error (this
> should be on the bloody homepage of freetds.org :)

Setting the character set in [global] is unlikely to work. It's suprising it
had any effect. Another recently discussed topic and one which might be
changing in the futureā€¦

You have to set it specifically inside a server section.

That's why I was careful to note that you have to set all the server
parameters there:

>> You need to set up the server's parameters (host name, port, tds version,
>> etc) in the freetds.conf file, and then you can also specify the "client
>> charset" option there.

And make sure your TDS version is at least 7.0.
Or, really, to spare us some future emails, depending on FreeTDS and SQL
Server version, you might also find that exactly 7.0 is the only one which
will work.

The stable FreeTDS version is so stable it hasn't been updated in years. :)

> fretds.log says:
> token.c:2356:server indicated charset change to "iso_1"

These seem to indicate TDS version 4.2 or 5.0.

You could try
TDSDUMPCONFIG=stdout ./your-script-here.pl

and see how it's picking up the configuration parameters.





Archive powered by MHonArc 2.6.24.

Top of Page