FreeTDS Development Group

["James K. Lowden" <jklowden AT schemamania.org>]

On Thu, 28 Oct 2004 22:12:59 -0500, Chuck Bearden <cfbearden AT gmail.com>
wrote:
> > > I can provide a TDSDUMP log of this if it would be helpful.
> > 
> > You guessed it.  ;-)
> 
> Here it is:
> 
>   <http://acad24.sahs.uth.tmc.edu/tdslog/tdsdump.log.txt>

Ach, du lieber.  You didn't say you were passing UTF-8 as parameters to a
stored procedure.  :-(

AIUI, there's some issue with iconv and parameter passing.  Or was.  There
was a thread on the subject recently.  I don't see anything in ChangeLog. 


Please try with inline code to confirm that's the issue.  Perhaps Frediano
will be able to shed some more light.  

> My only interest in UCS-2 was due to the hope that, if the server
> likes UCS-2, I could bypass conversion issues by feeding it UCS-2.  If
> I can make the loading work with UTF-8 I'll be perfectly happy.

We made it pretty hard to bypass.  Conversion is done in libtds near the
wire-handling code; the server's encoding has a short lifetime on the
client side.  

One workaround for now might be to bcp the data into a staging table, and
call your stored procedure once per row.  That should at least work.  

Regards, 

--jkl