On 7/6/06, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
...
>> Yes, its actually quite esay: you dump as you feel apropriate,
>> then create the database with the encoding you want,
>> restore w/o creating database and you are done.
>> Restore sets the client encoding to what it actually was
>> in
...
Yes, its actually quite esay: you dump as you feel apropriate,
then create the database with the encoding you want,
restore w/o creating database and you are done.
Restore sets the client encoding to what it actually was
in the dump data (in your case latin-1) and the database
would be utf-8
On 7/6/06, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
Marco Bizzarri schrieb:
> Hi all.
>
> Here is my use case: I've an application which uses PostgreSQL as
> backend. Up to now, the database was encoded in SQL_ASCII or LATIN1.
> Now, we need to migrate to UTF-8.
>
> What we tried, was to:
>
> 1
Marco Bizzarri schrieb:
Hi all.
Here is my use case: I've an application which uses PostgreSQL as
backend. Up to now, the database was encoded in SQL_ASCII or LATIN1.
Now, we need to migrate to UTF-8.
What we tried, was to:
1) dump the database using pg_dump, in tar format (we had blob);
2) mo
Hi all.
Here is my use case: I've an application which uses PostgreSQL as
backend. Up to now, the database was encoded in SQL_ASCII or LATIN1.
Now, we need to migrate to UTF-8.
What we tried, was to:
1) dump the database using pg_dump, in tar format (we had blob);
2) modifying the result, using
