Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VN7jJ-0006zE-5L for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Sep 2013 20:55:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VN7jI-00054b-LZ for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Sep 2013 20:55:08 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VN7jH-00053o-26 for pgsql-hackers@postgresql.org; Fri, 20 Sep 2013 20:55:07 +0000 Received: from eisentraut.org ([85.214.91.16] helo=gattler.pezone.net) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VN7jE-0002gu-D5 for pgsql-hackers@postgresql.org; Fri, 20 Sep 2013 20:55:06 +0000 Received: from jesse.mybdev.com (unknown [204.145.120.11]) by gattler.pezone.net (Postfix) with ESMTPSA id B90DC59000F; Fri, 20 Sep 2013 20:55:01 +0000 (UTC) Message-ID: <523CB625.5020905@gmx.net> Date: Fri, 20 Sep 2013 16:55:01 -0400 From: Peter Eisentraut User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Robert Haas CC: MauMau , Tom Lane , "Boguk, Maksym" , Heikki Linnakangas , "pgsql-hackers@postgresql.org" Subject: Re: UTF8 national character data type support WIP patch and list of open issues. References: <522594E8.2050106@vmware.com> <904.1378304922@sss.pgh.pa.us> <37B76474BB3149FD841373E12E355851@maumau> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 9/20/13 2:22 PM, Robert Haas wrote: >>> I am not keen to introduce support for nchar and nvarchar as >>> >> differently-named types with identical semantics. >> > >> > Similar examples already exist: >> > >> > - varchar and text: the only difference is the existence of explicit length >> > limit >> > - numeric and decimal >> > - int and int4, smallint and int2, bigint and int8 >> > - real/double precison and float > I agree that the fact we have both varchar and text feels like a wart. > The other examples mostly involve different names for the same > underlying type, and so are different from what you are asking for > here. Also note that we already have NCHAR [VARYING]. It's mapped to char or varchar, respectively, in the parser, just like int, real, etc. are handled. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers