| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | MauMau <maumau307(at)gmail(dot)com> |
| Cc: | robertmhaas(at)gmail(dot)com, Tatsuo Ishii <ishii(at)postgresql(dot)org>, 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-23 21:26:42 |
| Message-ID: | 5240B212.8040307@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/23/13 2:53 AM, MauMau wrote:
> Yes, I believe you are right. Regardless of whether we support multiple
> encodings in one database or not, a single client encoding will be
> sufficient for one session. When receiving the "Q" message, the whole
> SQL text is converted from the client encoding to the database
> encoding. This part needs no modification. During execution of the "Q"
> message, NCHAR values are converted from the database encoding to the
> NCHAR encoding.
That assumes that the conversion client encoding -> server encoding ->
NCHAR encoding is not lossy. I thought one main point of this exercise
was the avoid these conversions and be able to go straight from client
encoding into NCHAR.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-09-23 21:36:26 | Re: record identical operator |
| Previous Message | Peter Eisentraut | 2013-09-23 21:03:59 | Re: logical changeset generation v6 |