On Thu, Jan 29, 2015 at 5:30 PM, Andrew Dunstan <and...@dunslane.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
