X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B0C805378A for ; Sun, 15 May 2005 13:16:18 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 40978-01 for ; Sun, 15 May 2005 16:16:14 +0000 (GMT) Received: from web31008.mail.mud.yahoo.com (web31008.mail.mud.yahoo.com [68.142.200.171]) by svr1.postgresql.org (Postfix) with SMTP id 42EBF533FA for ; Sun, 15 May 2005 13:16:13 -0300 (ADT) Received: (qmail 86927 invoked by uid 60001); 15 May 2005 16:16:13 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=qhBIDngPKOVjJS3ASHPW1QXb1qNd9EjniRWjbq/SPuO5KFpty2QBgUMmcE4SHvNfIV4jojDuRIaOVIo2QNtuW/wxUICuiAJYj43FzvxXt5yyIaEr/J8ypPPffv6qqJBdY490eOVIRrB6Gxa5LL8bVjSRhI9ZaTEFc4NW6PMFqJQ= ; Message-ID: <20050515161613.86925.qmail@web31008.mail.mud.yahoo.com> Received: from [210.211.162.193] by web31008.mail.mud.yahoo.com via HTTP; Sun, 15 May 2005 09:16:13 PDT Date: Sun, 15 May 2005 09:16:13 -0700 (PDT) From: Rajesh Mallah Subject: Re: Significance of Database Encoding [ update ] To: pgsql-sql@postgresql.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=4.512 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, FORGED_YAHOO_RCVD, RCVD_IN_NJABL_PROXY X-Spam-Level: **** X-Archive-Number: 200505/104 X-Sequence-Number: 21417 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 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 | > +--------------------------------------------------------------------------------------+ > | 私はガラス > > | > +--------------------------------------------------------------------------------------+ > > 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