Re: [SQL] Understanding Encoding

2013-09-06 Thread Beena Emerson
Hello, Thank you all. Amit, Changing the encoding of the terminal emulator worked. Sebastiean, the tip was helpful. -- Beena Emerson

Re: [SQL] Understanding Encoding

2013-09-06 Thread Sebastien FLAESCH
Hi, Tip: To identify what encoding you enter in the psql command interpreter: 1) Open a file with vim 2) Type in you SQL or copy/paste 3) Save the file and quit vim 4) $ file Should give you the encoding of that text file. For ex: sf@orca:~$ echo $LC_ALL en_US.UTF-8 sf@orca:~$ cat /tmp/xx

Re: [SQL] [NOVICE] Understanding Encoding

2013-09-06 Thread Beena Emerson
On Fri, Sep 6, 2013 at 12:29 PM, Tom Lane wrote: > Beena Emerson writes: > > It still gives same result: > > > $ LANG=ko_KR LC_ALL=ko_KR > > $ psql -d korean > > > korean=# SHOW client_encoding; > > client_encoding > > - > > EUC_KR > > (1 row) > > > korean=# INSERT INTO tbl VAL

Re: [SQL] [NOVICE] Understanding Encoding

2013-09-06 Thread Amit Langote
On Fri, Sep 6, 2013 at 3:47 PM, Beena Emerson wrote: > >> >> I wonder if you have tried changing your "locale" to ko_KR; something >> like: >> >> LANG=ko_KR LC_ALL=ko_KR \ >> psql -d korean >> > > Hi, > > It still gives same result: > > $ LANG=ko_KR LC_ALL=ko_KR > $ psql -d korean > > korean=# SHO

Re: [SQL] Understanding Encoding

2013-09-06 Thread Tatsuo Ishii
> Hello All, > > I am not able to understand how the encoding is handled. I would be happy > if someone can tell what is happening in the following scenario: > > 1. I have created a database with EUC_KR encoding and created a table and > inserted some korean value into it. > > =# CREATE DATABASE