| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | "Arulappan, Arul Shaji" <arul(at)fast(dot)au(dot)fujitsu(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal - Support for National Characters functionality |
| Date: | 2013-07-15 14:54:07 |
| Message-ID: | 51E40D0F.5080408@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/15/13 1:26 AM, Arulappan, Arul Shaji wrote:
> Yes, the idea is that users will be able to declare columns of type
> NCHAR or NVARCHAR which will use the pre-determined encoding type. If we
> say that NCHAR is UTF-8 then the NCHAR column will be of UTF-8 encoding
> irrespective of the database encoding. It will be up to us to restrict
> what Unicode encodings we want to support for NCHAR/NVARCHAR columns.
I would try implementing this as an extension at first, with a new data
type that is internally encoded differently. We have citext as
precedent for successfully implementing text-like data types in user space.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-07-15 15:00:59 | Re: Add more regression tests for dbcommands |
| Previous Message | Robert Haas | 2013-07-15 14:53:02 | Re: vacuumlo - use a cursor |