Re: Other Characterset to UTF8

From: John DeSoi <desoi(at)pgedit(dot)com>
To: Abu Mushayeed <amushayeed(at)hotmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Other Characterset to UTF8
Date: 2006-07-21 01:00:09
Message-ID: 2DA88E8B-72D7-4430-AC84-4976A40BBB66@pgedit.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


On Jul 20, 2006, at 5:54 PM, Abu Mushayeed wrote:

> 1. set client_encoding = 'LATIN1';
> 2. COPY <table_name> FROM '<dir_path/file_name' with NULL as ''
>
> The data gets into the database. The datbase has some inbuilt
> functions that translates the data from LATIN1 to UTF8.
>
> The question is it works but is this correct?

Yes, it is correct assuming the data in the file is really latin1 :).
You tell PostgreSQL what character set you are using on the client
side and it takes care of converting it to the encoding used for the
database.

John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Michael Grossman 2006-07-21 10:00:28 Task/Jobs issue
Previous Message Abu Mushayeed 2006-07-20 21:54:40 Other Characterset to UTF8