Skip to Content.
Sympa Menu

freetds - Re: [freetds] SQL Server version and TDS Version

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Craig A. Berry" <craigberry AT mac.com>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] SQL Server version and TDS Version
  • Date: Sun, 18 Apr 2010 18:29:25 -0500


On Apr 18, 2010, at 3:47 PM, James K. Lowden wrote:

Vinh Nguyen wrote:

Sure, here is a TDSDUMP when I specify TDS version 8:

log.c:190:Starting log file for FreeTDS 0.82
on 2010-04-18 12:42:52 with debug flags 0x4fff.
iconv.c:197:names for ISO-8859-1: ISO-8859-1
iconv.c:197:names for UTF-8: UTF-8
iconv.c:197:names for UCS-2LE: UCS-2LE
iconv.c:197:names for UCS-2BE: UCS-2BE
iconv.c:363:iconv to convert client-side data to the "utf-8" character
set iconv.c:432:tds_iconv_info_init: client charset name "" unrecognized

That doesn't look good. Are you using OS X's iconv(3)? It looks like it
wants the name in upper case. (Cf. line 197.)

I think FreeTDS doesn't know the encoding, decides it's "probably" ISO
8859-1 (wrongly) and mis-encodes something in your login packet, causing
the server to reject it.

Here are the options I see for Mac OS X (Leopard PPC, if it matters):

% iconv -l | grep -i utf\.8
UTF-8 UTF8
UTF-8-MAC UTF8-MAC

So the question probably is who or what thinks it wants utf-8 rather than UTF-8? If that setting came from a freetds.conf, the answer is easy -- don't do that. If it's a default chosen by FreeTDS, that surprises me because I though all of the common mappings had long since been worked out.

________________________________________
Craig A. Berry
mailto:craigberry AT mac.com

"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser





Archive powered by MHonArc 2.6.24.

Top of Page