Skip site navigation (1) Skip section navigation (2)

Re: JSON for PG 9.2

From: Abhijit Menon-Sen <ams(at)toroid(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>,Peter Eisentraut <peter_e(at)gmx(dot)net>,Andrew Dunstan <andrew(at)dunslane(dot)net>,Jeff Janes <jeff(dot)janes(at)gmail(dot)com>,Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>,"David E(dot) Wheeler" <david(at)kineticode(dot)com>,Claes Jakobsson <claes(at)surfar(dot)nu>,Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>,Merlin Moncure <mmoncure(at)gmail(dot)com>,Magnus Hagander <magnus(at)hagander(dot)net>,Jan Urbański <wulczer(at)wulczer(dot)org>,Simon Riggs <simon(at)2ndquadrant(dot)com>,Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org,Jan Wieck <janwieck(at)yahoo(dot)com>
Subject: Re: JSON for PG 9.2
Date: 2012-02-02 14:51:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
At 2012-02-02 08:54:32 -0500, robertmhaas(at)gmail(dot)com wrote:
> Someone is eventually going to propose a function with a  name like
> json_to_string() which, when given this JSON object, returns a
> three-character string with the PostgreSQL text type. 

Ah, that's the bit I was missing. I thought you were talking about an
immediate error condition.

> That's useful and I support it.

Agreed. Also, now I understand that you are saying that json_to_string()
(json_string_to_text?) would fail if the result couldn't be represented
as a text in the current encoding, and that's sensible as well. I had
misunderstood "is going to admit of a number of error…" in your mail.

As for surrogate pairs, just to be clear, what I was proposing earlier
in the thread was to change json.c:json_lex_string() to detect errors
(e.g. only one half of a surrogate pair, which is the commonest error
I've encountered in the wild) and reject such strings.

Thanks for the explanation.

-- ams

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-02-02 15:10:12
Subject: Re: keywords in initdb are case-sensitive?
Previous:From: Robert HaasDate: 2012-02-02 14:41:46
Subject: Re: patch for implementing SPI_gettypemod()

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group