From: | "Marco Bizzarri" <marco(dot)bizzarri(at)gmail(dot)com> |
---|---|
To: | "Tomi NA" <hefest(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Changing encoding of a database |
Date: | 2006-06-21 08:17:36 |
Message-ID: | 3f0d61c40606210117t791d1fcfq6561d86b5cf162a4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tomi.
Thanks for your answer, I was not aware of such a tool.
The next question at this point is (of course): what is the problem if
I have blob? Should I recode them as well?
Regards
Marco
On 6/20/06, Tomi NA <hefest(at)gmail(dot)com> wrote:
> On 6/19/06, Marco Bizzarri <marco(dot)bizzarri(at)gmail(dot)com> wrote:
> > I all.
> >
> > We've PostgreSQL database, with SQL_ASCII or LATIN1 encoding. We would
> > like to migrate them to UNICODE. Is there some contributed/available
> > script, or this is something we should do at hand?
> >
> > Regards
> > Marco
>
> If you don't have blobs in your database, dump it to insert
> statements, use the recode tool to recode your data, create a new
> database based on UTF8 and load the data.
>
> t.n.a.
>
--
Marco Bizzarri
http://notenotturne.blogspot.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2006-06-21 08:31:40 | Re: Computing transitive closure of a table |
Previous Message | Jad Madi | 2006-06-21 07:39:31 | unsubscribe |