Re: unicode

Hi,
I am trying to generate a TDSDUMP log, but it never produces a file for
me.  I followed these instructions:

TDSDUMP
Log files can be turned on using the TDSDUMP environment variable. For
instance, setting the location of a dumpfile 

$ export TDSDUMP=/tmp/freetds.log Will generate a log file named
freetds.log in the /tmp directory.

I also tried some settings in freetds.conf to get a log file....but
still no log file:

[jjptrng]
        host = xx.xx.x.xx   <---didn't want to post our ip....:)
        port = 1433
        tds version = 8.0
        client charset = UTF-8
        dump file = /opt/oracle/odbc/etc/freetds.log
        debug level = 10
        dump file append = yes


Any ideas?
Laurie

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of James K. Lowden
Sent: Wednesday, July 23, 2008 12:16 PM
To: FreeTDS Development Group
Subject: Re: [freetds] unicode

Murray, Laura (US) wrote:
> If I take the N away, the insert works fine, but the characters are
> garbled during transmission, of course.  Actually to be more specific,
> some of the Asian characters appear properly on the SQL Server side,
but
> others appear as little boxes.

Can you do:

	select cast(<colname> as binary) 
	from [email protected]
	where <key> = 'FTR1'
	-- or whatever produces one row

on SQL Server and on Oracle, so we can compare the difference?  Also, a
TDSDUMP log of the insert flowing to SQL Server will be illuminating.  

I think you may be completely stuck. If 

1.  your gateway depends on compatible SQL implementations, and 
2.  Microsoft requires the 'N' prefix, and 
3.  Oracle prohibits it, then 

it's hard to see what anyone can do. 

--jkl
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds


This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior 
permission.  We have taken precautions to minimize the risk of transmitting 
software viruses, but we advise you to carry out your own virus checks on 
any attachment to this message.  We cannot accept liability for any loss 
or damage caused by software viruses.  The information contained in this 
communication may be confidential and may be subject to the attorney-client 
privilege. If you are the intended recipient and you do not wish to receive 
similar electronic messages from us in the future then please respond to the 
sender to this effect.