Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M236535=pgsql-hackers-arkari@postgresql.org>)
 id 1Vdo6l-0001Uv-TW
 for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2013 21:24:20 +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+M236535=pgsql-hackers-arkari@postgresql.org>)
 id 1Vdo6k-0007qj-Mt
 for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2013 21:24:18 +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 1Vdo6j-0007qa-6e
 for pgsql-hackers@postgresql.org; Tue, 05 Nov 2013 21:24:17 +0000
Received: from mail-pa0-x235.google.com ([2607:f8b0:400e:c03::235])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>)
 id 1Vdo6g-0003xy-HL; Tue, 05 Nov 2013 21:24:16 +0000
Received: by mail-pa0-f53.google.com with SMTP id kx10so9469640pab.40
 for <multiple recipients>; Tue, 05 Nov 2013 13:24:12 -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=OI6qnkbeiJ/5K/4Jqu9NMhif8gL9K/Kz9aFWKn+muBw=;
 b=mCzHbHOVcD+sfIDJitY/vwMtF7U85pOGog00OOowfg8bmyNKO5q3mCcYx79ohffdhB
 TciXIzspLnUwRFMqDH4eAFyiGrdmUk4ok4tSHR+93M/7SzNlLYGbIA7kJ4ocKkBzHqf9
 dDyECCwE8t32hGQ1itaoxhq62CJC0CEd3yRQBY6QCSM/E1NH/vqzAq/sT4Vx5z62SRRR
 WKiXMh+fwKELZb/ciXzKYTz0iGruEotbBdxCO7Ml53Q+43tu33QBUQxvzcOuaUUdgYHH
 RlN72Xnpo/7Ha4HiMKihJii5Z+dlXD9xcAqmyLZn8p0HvxwkG3za2Fc9rlZ9k4FSl9Th
 uFYQ==
X-Received: by 10.66.27.201 with SMTP id v9mr336321pag.15.1383686652092;
 Tue, 05 Nov 2013 13:24:12 -0800 (PST)
Received: from maumau (p6019-ipbfp211sizuokaden.shizuoka.ocn.ne.jp.
 [114.170.213.19])
 by mx.google.com with ESMTPSA id fk4sm42710111pab.23.2013.11.05.13.24.08
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Tue, 05 Nov 2013 13:24:11 -0800 (PST)
Message-ID: <56B1EFF4F25747628882CDFB8B909281@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>
 <6C7E3D3C38CE4E0BAF20269F7E2DBA21@maumau>
 <A737B7A37273E048B164557ADEF4A58B17C56755@ntex2010i.host.magwien.gv.at>
In-Reply-To: 
 <A737B7A37273E048B164557ADEF4A58B17C56755@ntex2010i.host.magwien.gv.at>
Subject: Re: UTF8 national character data type support WIP patch and list of
 open issues.
Date: Wed, 6 Nov 2013 06:25:30 +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>
> I looked into the Standard, and it does not have NVARCHAR.
> The type is called NATIONAL CHARACTER VARYING, NATIONAL CHAR VARYING
> or NCHAR VARYING.

OUch, that's just a mistake in my mail.  You are correct.


> > I guess that the goal of this patch is to support Oracle syntax.
> But anybody trying to port CREATE TABLE statements from Oracle
> is already exposed to enough incompatibilities that the difference between
> NVARCHAR and NCHAR VARYING will not be the reason to reject PostgreSQL.
> In other words, I doubt that introducing the nonstandard NVARCHAR
> will have more benefits than drawbacks (new reserved word).

Agreed.  But I'm in favor of supporting other DBMS's syntax if it doesn't 
complicate the spec or implementation too much, because it can help migrate 
to PostgreSQL.  I understand PostgreSQL has made such efforts like PL/pgSQL 
which is similar to PL/SQL, text data type, AS in SELECT statement, etc.


> But I don't think that this requires the first step that your patch
> implements, it is in fact orthogonal.

(It's not "my" patch.)


> Regarding the Standard compliant names of these data types, PostgreSQL
> already supports those.  Maybe some documentation would help.
>
> I don't think that there is any need to change NCHAR even if we
> get per-column encoding, it is just syntactic sugar to support
> SQL Feature F421.

Maybe so.  I guess the distinct type for NCHAR is for future extension and 
user friendliness.  As one user, I expect to get "national character" 
instead of "char character set xxx" as output of psql \d and pg_dump when I 
specified "national character" in DDL.  In addition, that makes it easy to 
use the pg_dump output for importing data to other DBMSs for some reason.


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