From: Ivo Rossacher <rossacher@bluewin.ch>
To: pgsql-admin@postgresql.org
Subject: Re: Changing encoding
Date: Tue, 15 Jul 2008 19:26:13 +0200
Message-ID: <200807151926.13848.rossacher@bluewin.ch> (raw)
In-Reply-To: <DA753240-4B27-402B-9C18-9404E7B8773A@indiana.edu>
References: <DA753240-4B27-402B-9C18-9404E7B8773A@indiana.edu>
For the SQL_ASCII tables it depends what was actually written to the tables.
SQL_ASCII means that the server does not do any conversation and that the
client is responsible for the used encoding. So if there is data in the table
with different encodings (comming from different clients with different
encodings) you need to fix this by hand (depending on the data size an
editor, iconv, recode or similar might help you with this).
The Latin1 tables might be fixed by iconv or be autodetected by the server.
You can find details about the subject in the chapter 21.2 Character Set
Support of the server documentation.
Best regards
Ivo
Am Dienstag, 15. Juli 2008 16:14:25 schrieb Carol Walter:
> Hello,
>
> I have some databases that use SQL ASCII or Latin1 encoding that need
> to be UTF8. When I have drop the database and recreated it with the
> correct encoding I get errors in restoring the data. How is this done?
>
> Carol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rossacher@bluewin.ch
Subject: Re: Changing encoding
In-Reply-To: <200807151926.13848.rossacher@bluewin.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox