| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Tatsuo Ishii" <ishii(at)postgresql(dot)org> |
| Cc: | <robertmhaas(at)gmail(dot)com>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <maksymb(at)fast(dot)au(dot)fujitsu(dot)com>, <hlinnakangas(at)vmware(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UTF8 national character data type support WIP patch and list of open issues. |
| Date: | 2013-09-20 23:58:15 |
| Message-ID: | 25023FC76F8940619C3780B99E733D24@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>
> As far as I can tell the whole reason for introducing NCHAR is to
> support SHIFT-JIS, there hasn't been call for any other encodings, that
> I can remember anyway.
Could you elaborate on this, giving some info sources?
> So rather than this whole NCHAR thing, why not just add a type
> "sjistext", and a few type casts and call it a day...
The main reason for supporting NCHAR types is to ease migration from other
DBMSs, not requiring DDL changes. So sjistext does not match that purpose.
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2013-09-21 00:07:13 | Re: UTF8 national character data type support WIP patch and list of open issues. |
| Previous Message | MauMau | 2013-09-20 23:33:28 | Re: UTF8 national character data type support WIP patch and list of open issues. |