From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: nested hstore patch |
Date: | 2014-01-10 18:29:50 |
Message-ID: | CA+TgmoYLJ79Jiedirf6zHDGSyT+Kbb6q+tHL+5OKU-8BAg_4eQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 9, 2014 at 5:08 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> * I have replicated all the json processing functions for jsonb
> (although not the json generating functions, such as to_json). Most
> of these currently work by turning the jsonb back into json and then
> processing as before. I am sorting out some technical issues and
> hope to have all of these rewritten to use the native jsonb API in a
> few days time.
> * We still need to document jsonb. That too I hope will be done quite
> shortly.
> * The jsonb regression test currently contains U+ABCD - I guess we'd
> better use some hex encoding or whatever for that - unlike json, the
> jsonb de-serializer dissolves unicode escapes.
How does that work if the server encoding isn't UTF-8?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Freire | 2014-01-10 18:35:34 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
Previous Message | Tom Lane | 2014-01-10 18:27:22 | Re: new json funcs |