Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M236485=pgsql-hackers-arkari@postgresql.org>)
 id 1VdfnI-00062n-Gf
 for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2013 12:31:40 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M236485=pgsql-hackers-arkari@postgresql.org>)
 id 1VdfnH-0004cO-Rz
 for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2013 12:31:39 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>) id 1VdfnG-0004cG-S1
 for pgsql-hackers@postgresql.org; Tue, 05 Nov 2013 12:31:39 +0000
Received: from mail-pd0-x230.google.com ([2607:f8b0:400e:c02::230])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>)
 id 1VdfnD-0002ct-JK; Tue, 05 Nov 2013 12:31:38 +0000
Received: by mail-pd0-f176.google.com with SMTP id g10so8286188pdj.21
 for <multiple recipients>; Tue, 05 Nov 2013 04:31:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:from:to:cc:references:in-reply-to:subject:date
 :mime-version:content-type:content-transfer-encoding;
 bh=DZc3RihrZwTH/ZApcp8HYcGz7wG1T1mIRLmxd3MQGwM=;
 b=BFkrwl/D+4a+2VEnLP8rhlQIupsm4Mc4j2ZOZjikK+1yT8Fq42O+xvTqCT0bJ9vaBr
 i8bO6y8QXppGJI63IjIlCBz7qUAi3qEpXE+8qcLRLMWa9wNV0MiUMOamuKzbRrHYiaaU
 P89K7OysolqhjChIUQT58PCWeoNtRN3HLkTClPnZ37ZbjXc8lzjCF1xJFTX4gGG+UB8o
 PBIRWvxYdalnCe4ExdivczY+Hv0mmWsWKGruUxow3Ltgsu9rfWrt+jgNPWOwQdSr/4Zo
 DCO/c28fv+d/2Uj0LFgQRmYvBO5vKKL5rO8YN+cqKCpweRngGxag0lwbG82mAGsdGgQz
 +fGg==
X-Received: by 10.66.170.138 with SMTP id am10mr22294625pac.51.1383654692842;
 Tue, 05 Nov 2013 04:31:32 -0800 (PST)
Received: from maumau (p6019-ipbfp211sizuokaden.shizuoka.ocn.ne.jp.
 [114.170.213.19])
 by mx.google.com with ESMTPSA id er3sm34358467pbb.40.2013.11.05.04.31.29
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Tue, 05 Nov 2013 04:31:31 -0800 (PST)
Message-ID: <6C7E3D3C38CE4E0BAF20269F7E2DBA21@maumau>
From: "MauMau" <maumau307@gmail.com>
To: "Albe Laurenz" <laurenz.albe@wien.gv.at>,
 "Arulappan, Arul Shaji *EXTERN*" <arul@fast.au.fujitsu.com>,
 "Greg Stark" <stark@mit.edu>
Cc: "Peter Eisentraut" <peter_e@gmx.net>,
 "Robert Haas" <robertmhaas@gmail.com>,
 "Tatsuo Ishii" <ishii@postgresql.org>, "Tom Lane" <tgl@sss.pgh.pa.us>,
 "Boguk, Maksym" <Maksym.Boguk@au.fujitsu.com>,
 "Heikki Linnakangas" <hlinnakangas@vmware.com>,
 "PostgreSQL-development" <pgsql-hackers@postgresql.org>
References: 
 <CA+TgmobWv_96dSfSHv2ZJWSXAD=QTiBEKw-LT359sGArYe+AXQ@mail.gmail.com>
 <20130920.085853.1628917054830864151.t-ishii@sraoss.co.jp>
 <CA+TgmoZEy=pt2B5D+nuPAib7KvhNoBgRGYRWnkS4pyrqfcdYHQ@mail.gmail.com>
 <20130922.072952.1977066018971837040.t-ishii@sraoss.co.jp>
 <D0A2FE73E8354EDCBEE56EC79268CA4E@maumau> <5240B212.8040307@gmx.net>
 <7DCFAE8265254605840917B35EEF09F1@maumau>
 <CAM-w4HMRCTyemtmKDJPHL72dXH1Gr6q5JrkCNnE63RXLn02Tjw@mail.gmail.com>
 <7C2A735AFC3E4088A8F49B677855369C@maumau>
 <022C711CCA8AF2459F370E936F2B9E8C0255E4BB@SYDExchTmp.au.fjanz.com>
 <A737B7A37273E048B164557ADEF4A58B17C563E8@ntex2010i.host.magwien.gv.at>
In-Reply-To: 
 <A737B7A37273E048B164557ADEF4A58B17C563E8@ntex2010i.host.magwien.gv.at>
Subject: Re: UTF8 national character data type support WIP patch and list of
 open issues.
Date: Tue, 5 Nov 2013 21:32:49 +0900
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
X-Pg-Spam-Score: -1.3 (-)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

From: "Albe Laurenz" <laurenz.albe@wien.gv.at>
> If I understood the discussion correctly the use case is that
> there are advantages to having a database encoding different
> from UTF-8, but you'd still want sume UTF-8 columns.
>
> Wouldn't it be a better design to allow specifying the encoding
> per column?  That would give you more flexibility.

Yes, you are right.  In the previous discussion:

- That would be nice if available, but it is hard to implement multiple 
encodings in one database.
- Some people (I'm not sure many or few) are NCHAR/NVARCHAR in other DBMSs. 
To invite them to PostgreSQL, it's important to support national character 
feature syntactically and document it in the manual.  This is the first 
step.
- As the second step, we can implement multiple encodings in one database. 
According to the SQL standard, "NCHAR(n)" is equivalent to "CHAR(n) 
CHARACTER SET cs", where cs is an implementation-defined character set.


Regards
MauMau



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers