| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "Arulappan, Arul Shaji *EXTERN*" <arul(at)fast(dot)au(dot)fujitsu(dot)com>, "Greg Stark" <stark(at)mit(dot)edu> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tatsuo Ishii" <ishii(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Boguk, Maksym" <Maksym(dot)Boguk(at)au(dot)fujitsu(dot)com>, "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UTF8 national character data type support WIP patch and list of open issues. |
| Date: | 2013-11-05 12:32:49 |
| Message-ID: | 6C7E3D3C38CE4E0BAF20269F7E2DBA21@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-11-05 13:07:06 | Re: Failure while inserting parent tuple to B-tree is not fun |
| Previous Message | Heikki Linnakangas | 2013-11-05 12:06:26 | Re: [PATCH] configure: add git describe output to PG_VERSION when building a git tree |