On Fri, Jan 20, 2012 at 2:21 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> Err, actually, now that I think about it, that might be a problem: >> what happens if we're trying to test two characters for equality and >> the encoding conversion fails? > > This is surely all entirely doable given the encoding infrastructure > we already have. We might need some minor refactoring, eg to have > a way of not throwing an error, but it's not going to be that hard > to achieve if somebody wants to do it. So I still see little reason > for making the JSON type behave visibly differently in non-UTF8 database > encodings.
OK. It feels a little grotty to me, but I'll go with the flow. -- 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
