Skip to Content.
Sympa Menu

freetds - Re: [freetds] unicode

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Jason Young (Morgon)" <morgon AT mygamercard.net>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] unicode
  • Date: Tue, 22 Jul 2008 13:12:23 -0400

Laura,

FreeTDS does support Unicode using an iconv wrapper defined when you set the "client charset = UTF8" in freetds.conf like it sounds like you've done.

SQL Server is a pain in regards to sending UTF strings, as you'll need to prefix all of your quoted strings with capital N, for example:
INSERT INTO utf8_table (utf8string) VALUES (N'???')

Same if you're using stored procedures as well.

Someone tells me that this follows the ANSI standard -- why SQL Server only chooses to follow the standard when it's more of a pain to the user, I'll never know ;)

Hope this helps,
-Jason


Murray, Laura (US) wrote:
Hi,
We have been successfully using freetds to communicate from our Oracle
9.2 database to a SQL Server database for quite some time. We have
recently run into a problem, however, with Asian languages. Japanese
and Chinese characters appear properly in our Oracle database, but
become garbled when we try to send them to the SQL Server database using
freetds. Does freetds support Unicode? I saw something on the site
that said it did not, but then found another page that said that it
did....so I am not sure! I also found some postings about getting
around this problem by setting the client charset = GB2312 in the
freetds.conf file. I tried that and also tried setting it to UTF-8.
Neither worked. In our freetds.conf file it lists our tds version as 8.0
Thanks in advance for any help!
--Laurie

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.
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds




Archive powered by MHonArc 2.6.24.

Top of Page