Re: UTF8 national character data type support WIP patch and list of open issues. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: UTF8 national character data type support WIP patch and list of open issues.
Date
Msg-id CA+TgmoaT-h5C25LXd1DgfyiW2t9K92eVdVcJHC_1We0JpJFqgg@mail.gmail.com
Whole thread Raw
In response to Re: UTF8 national character data type support WIP patch and list of open issues.  ("MauMau" <maumau307@gmail.com>)
Responses Re: UTF8 national character data type support WIP patch and list of open issues.
List pgsql-hackers
On Wed, Sep 18, 2013 at 6:42 PM, MauMau <maumau307@gmail.com> wrote:
>> It seems to me that these two points here are the real core of your
>> proposal.  The rest is just syntactic sugar.
>
> No, those are "desirable if possible" features.  What's important is to
> declare in the manual that PostgreSQL officially supports national character
> types, as I stated below.

That may be what's important to you, but it's not what's important to
me.  I am not keen to introduce support for nchar and nvarchar as
differently-named types with identical semantics.  And I think it's an
even worse idea to introduce them now, making them work one way, and
then later change the behavior in a backward-incompatible fashion.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PERFORM] encouraging index-only scans
Next
From: Robert Haas
Date:
Subject: Re: [RFC] Extend namespace of valid guc names