pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Mallah <mallah_rajesh@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: Re: Significance of Database Encoding [ update ]
Date: Sun, 15 May 2005 09:16:13 -0700 (PDT)
Message-ID: <20050515161613.86925.qmail@web31008.mail.mud.yahoo.com> (raw)



I am not sure why the characters did not display properly
in the mailling list archives.

http://archives.postgresql.org/pgsql-sql/2005-05/msg00102.php

but when i do the select in my screen (xterm -u8) i do 
see the japanese glyphs properly.


Regds
Mallah.




--- Rajesh Mallah <mallah_rajesh@yahoo.com> wrote:
> 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                                                 |
> +--------------------------------------------------------------------------------------+
> | &#31169;&#12399;&#12460;&#12521;&#12473;                                                      
>  
>                     |
> +--------------------------------------------------------------------------------------+
> 
> 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 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
> 


		
Discover Yahoo! 
Find restaurants, movies, travel and more fun for the weekend. Check it out! 
http://discover.yahoo.com/weekend.html 




Message-ID: <20050515161613.86925.qmail@web31008.mail.mud.yahoo.com>
Permalink:  ../20050515161613.86925.qmail@web31008.mail.mud.yahoo.com/
Also on:    postgresql.org/message-id/20050515161613.86925.qmail@web31008.mail.mud.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: mallah_rajesh@yahoo.com
  Subject: Re: Significance of Database Encoding [ update ]
  In-Reply-To: <20050515161613.86925.qmail@web31008.mail.mud.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox