X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DC77452972 for ; Fri, 6 May 2005 10:50:01 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10596-09 for ; Fri, 6 May 2005 13:49:52 +0000 (GMT) Received: from mta10.nationwireless.net (mta10.nationwireless.net [63.163.128.10]) by svr1.postgresql.org (Postfix) with ESMTP id DA5885340B for ; Fri, 6 May 2005 10:49:51 -0300 (ADT) Received: from jfradkin [63.162.100.127] by mta10.nationwireless.net with ESMTP (SMTPD-8.20) id A60207EC; Fri, 06 May 2005 09:49:54 -0400 From: "Joel Fradkin" To: Subject: encoding Date: Fri, 6 May 2005 09:50:06 -0400 Message-ID: <000001c55242$82e0fff0$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C55220.FBCF5FF0" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.549 tagged_above=0 required=5 tests=AWL, HTML_MESSAGE, MSGID_DOLLARS X-Spam-Level: * X-Archive-Number: 200505/52 X-Sequence-Number: 21365 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C55220.FBCF5FF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am not clear on what makes this work? =20 I am going live Sunday and have thus far been using SQL_ASCHII. I still have the feeling I should be using something else, but when I = used Unicode my conversion from MSSQL blew up on encoding error for a char = that wasn't plain ASCHII(IE French or Spanish etc.). The conversion program ran fine when I chose SQL_ASCHII.=20 The data is on a windows 2k MSSQL database. The conversion program is a .net app that reads from MSSQL win2k data = base and writes to postgtres 8.0.2 on Redhat AS4. I tried to get this to work a while back and found if I set the encoding explicitly on the connect in the .net connector it did not give me an = error, but I still have many asp pages and I could not get the encoding set = using the ODBC (which is what the asp pages use). I believe I tried setting it with a sql statement, but that did not seem = to help either. I can move forward using SQL_ASCHII, but would prefer to have encoding = set properly, but I ma not sure what I am missing. =20 Any ideas would be much appreciated. =20 Joel Fradkin =20 =20 =20 ------=_NextPart_000_0001_01C55220.FBCF5FF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am not clear on what makes this = work?

 

I am going live Sunday and have thus far been using = SQL_ASCHII.

I still have the feeling I should be using something = else, but when I used Unicode my conversion from MSSQL blew up on encoding = error for a char that wasn’t plain ASCHII(IE French or Spanish = etc.).

The conversion program ran fine when I chose = SQL_ASCHII.

The data is on a windows 2k MSSQL = database.

The conversion program is a .net app that reads from = MSSQL win2k data base and writes to postgtres 8.0.2 on Redhat = AS4.

I tried to get this to work a while back and found if = I set the encoding explicitly on the connect in the .net connector it did not = give me an error, but I still have many asp pages and I could not get the = encoding set using the ODBC (which is what the asp pages use).

I believe I tried setting it with a sql statement, = but that did not seem to help either.

I can move forward using SQL_ASCHII, but would prefer = to have encoding set properly, but I ma not sure what I am = missing.

 

Any ideas would be much = appreciated.

 

Joel Fradkin

 


 

 

------=_NextPart_000_0001_01C55220.FBCF5FF0--