X-Original-To: pgsql-jdbc-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 434A3D1B199; Sun, 18 Jul 2004 16:38:14 -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 46493-09; Sun, 18 Jul 2004 19:38:10 +0000 (GMT) Received: from mail.svhost.com.ar (mail.svhost.com.ar [200.80.239.22]) by svr1.postgresql.org (Postfix) with ESMTP id 8443AD1B170; Sun, 18 Jul 2004 16:38:07 -0300 (ADT) Received: from sistemat.com.ar (devel.sistemat.com.ar [192.168.1.40]) by mail.svhost.com.ar (Postfix) with ESMTP id 5AD1B20C08; Sun, 18 Jul 2004 16:36:24 -0300 (ART) Message-ID: <40FAD3C8.3080503@sistemat.com.ar> Date: Sun, 18 Jul 2004 16:47:20 -0300 From: "Dario V. Fassi" Organization: SISTEMATICA ingenieria de software srl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: es, es-ar, en-us, en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Cc: "pgsql-jdbc@postgresql.org" Subject: Re: [ADMIN] Migrate postgres databases from SQL_ASCII to UNICODE References: <40F98613.1060405@sistemat.com.ar> <16994.1090099096@sss.pgh.pa.us> <40F9B599.6080205@sistemat.com.ar> <28179.1090132144@sss.pgh.pa.us> In-Reply-To: <28179.1090132144@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------010008000108050309040207" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_20_30, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200407/231 X-Sequence-Number: 10615 This is a multi-part message in MIME format. --------------010008000108050309040207 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Tom Lane wrote: >"Dario V. Fassi" writes: > > >>>SQL_ASCII is not an encoding (it's more like the absence of knowledge >>>about an encoding). What is the data actually stored as? >>> >>> >>Yes you are right , the original data come from a DB2 with CodePage >>IBM-850 and was inserted without complains in a Postgres 7.3.6 with >>SQL_ASCII. >> >> > >Ugh. You'll have to work out how to convert that codepage to one of the >encodings that PG supports. Or else add it as a supported encoding >(I'm not sure how hard that is, but it's not out of the question). > > regards, tom lane > > Ok, I'm interested is do that , but someone is the development group would give me some assistence to get a start point to work with. I program in Java, C, and less frequently in C++. Dario. --------------010008000108050309040207 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Tom Lane wrote:
"Dario V. Fassi" <software@sistemat.com.ar> writes:
  
SQL_ASCII is not an encoding (it's more like the absence of knowledge
about an encoding).  What is the data actually stored as?
      
Yes you are right , the original data come from a DB2 with CodePage 
IBM-850  and was inserted  without complains in a Postgres 7.3.6 with 
SQL_ASCII.
    

Ugh.  You'll have to work out how to convert that codepage to one of the
encodings that PG supports.  Or else add it as a supported encoding
(I'm not sure how hard that is, but it's not out of the question).

			regards, tom lane
  
Ok, I'm interested is do that , but someone is the development group would give me some assistence to get a start point to work with.
I program in Java, C, and less frequently in C++.

Dario.


--------------010008000108050309040207--