| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb, unicode escapes and escaped backslashes |
| Date: | 2015-01-30 02:59:02 |
| Message-ID: | CA+TgmoZx4tGxd8mgOwWVUVYdtMeA0Oy=4=ubnJ++3NZfFyL-bw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 29, 2015 at 5:30 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> jsonb stores string values as postgres text values, with the unicode escapes
> resolved, just as it also resolves numbers and booleans into their native
> representation. If you want the input perfectly preserved, use json, not
> jsonb. I think that's made pretty clear in the docs.
>
> so text->jsonb->text is not and has never been expected to be a noop.
If you can't store text in a jsonb object and get it back out again,
it doesn't seem like a very useful data type.
Where exactly do you think this is documented?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-01-30 03:03:57 | Re: jsonb, unicode escapes and escaped backslashes |
| Previous Message | Robert Haas | 2015-01-30 02:55:22 | Re: Possible typo in create_policy.sgml |