From: | Rajesh Mallah <mallah_rajesh(at)yahoo(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Significance of Database Encoding |
Date: | 2005-05-15 15:33:37 |
Message-ID: | 20050515153337.11724.qmail@web31015.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi ,
I would want to know what is the difference between databases
that are created using UNICODE encoding and SQL_ASCII encoding.
I have an existing database that has SQL_ASCII encoding but
still i am able to store multibyte characters that are not
in ASCII character set. for example:
tradein_clients=# \l
List of databases
+-----------------+----------+-----------+
| Name | Owner | Encoding |
+-----------------+----------+-----------+
| template0 | postgres | SQL_ASCII |
| template1 | postgres | SQL_ASCII |
| tradein_clients | tradein | SQL_ASCII |
+-----------------+----------+-----------+
tradein_clients=# SELECT * from t_A;
+--------------------------------------------------------------------------------------+
| a |
+--------------------------------------------------------------------------------------+
| 私はガラス
|
+--------------------------------------------------------------------------------------+
Above is some japanese character.
I have seen some posting regarding migrating databases from
SQL_ASCII to UNICODE, given the above observation what
significance does a migration have.
Regards
Rajesh Kumar Mallah.
__________________________________
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
http://mobile.yahoo.com/learn/mail
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Mallah | 2005-05-15 16:16:13 | Re: Significance of Database Encoding [ update ] |
Previous Message | Ragnar Hafstað | 2005-05-13 22:43:19 | Re: Replacing a table with constraints |