| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | peter_e(at)gmx(dot)net |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why are there client-only encodings? |
| Date: | 2004-09-14 08:59:57 |
| Message-ID: | 20040914.175957.35012679.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I wanted to allow WIN1250 as a server-side encoding, in light of the
> Windows port. Now I wonder why there are client-only encodings at all.
> Without knowing details, it seems the client-only encodings are all
> "Windows world" encodings. So was the original reason not to allow
> these as server encodings that the server doesn't run on Windows? If
> so, should the category client-only encodings be abolished?
I think it's not just possible for some multi-byte encodings such as
SJIS(Shift-JIS) and Big5. Currently PostgreSQL will not accept them
because of they include special ASCII characters such as back slashes.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Schuchardt | 2004-09-14 09:02:18 | Re: beta1 & beta2 & Windows & heavy load |
| Previous Message | strk | 2004-09-14 08:59:06 | gist cost estimator failing |