Karsten Hilbert wrote:
> Tom Lane wrote:
> > To make libpq UTF-16 capable, we'd have to change its API for all
> > strings; either make the strings counted rather than null-terminated,
> > or make the string elements wchar instead of char. After that we'd
> > have to hack the FE/BE protocol too (or more likely, require libpq
> > to translate UTF-16 to UTF-8 before sending to the server). I don't
> > foresee anyone doing any of this, at least not in the near term.
> Is there any *real* loss of functionality in not supporting
> UTF-16 ? If so *should* it be supported in, say, 9.0 ? If not,
> should there be a FAQ item saying why not ?
Is there a reason you have to use UTF16? Can't you convert to UTF8 on
input? (I have no idea myself.) Do other databases support both UTf8
and UTF16?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
