FreeTDS Development Group

["Adam Prime x443" <aprime AT brunico.com>]

I fixed the problem with the help provided by you guys.  it ended up being 
two-fold.

1) I needed to recompile DBD::Sybase using the new version of FreeTDS.
2) I needed to make sure the fields were ntext, not text (in this case)

Once that was done, changing the client charset fixed it up.  


-----Original Message-----
From: James K. Lowden [mailto:jklowden AT schemamania.org]
Sent: Thursday, October 28, 2004 10:53 PM
To: FreeTDS Development Group
Subject: Re: [freetds] Re: hex(92), freeTDS and MS SQL


"Adam Prime x443" <aprime AT brunico.com> wrote:
> 
> How can i figure out which version of freetds is actually being used?
> 
> DBD::Sybase was compiled against an older version but i thought that if
> i overwrote all the libraries with the new install that would be ok. 
> but i guess that depends on whether or not DBD::Sybase is statically or
> dynamically linked.  I think it's dynamically linked though because when
> i renamed the freetds directory DBD::Sybase broke.

The TDSDUMP log has included version information at the top since 9 Dec
2002, a little after 0.60 was released.  UTF-8 support and generalized
charset handling was introduced in 0.62.  So, your log should indicate the
version.  

Since you're running in a web server, it might be that your TDSDUMP log is
getting overwritten with each new connection.  You want "dump file append
= yes" in freetds.conf.  

--jkl

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds