From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)krosing(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: json accessors |
Date: | 2012-11-30 16:34:55 |
Message-ID: | 50B8E02F.5090509@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/30/2012 10:59 AM, Hannu Krosing wrote:
>
> Btw, how does current json type handle code pages - is json always
> utf-8 even when server encoding is not ?
>
> if so then we could at least have a shortcut conversion of json to
> utf8-text which can skip codepage changes.
>
>
IIRC json is stored and processed in the server encoding. Normally it
would make sense to have that be utf8. It is delivered to the client in
the client encoding.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2012-11-30 16:48:04 | Re: [PATCH] Patch to fix a crash of psql |
Previous Message | Tatsuo Ishii | 2012-11-30 16:29:06 | Re: [PATCH] Patch to fix a crash of psql |