Jim Nasby <jim.na...@bluetreble.com> writes:
> On 10/20/14, 11:16 AM, Andrew Dunstan wrote:
>> The JSON spec is quite clear on this. Leading and trailing commas are not
>> allowed. I would fight tooth and nail not to allow it for json (and by
>> implication jsonb, since they use literally the same parser - in fact we do
>> that precisely so their input grammars can't diverge).
> +1. Data types that implement specs should follow the spec.
> I was more concerned about things like polygon, but the real point (ha!) is
> that we need to think about the data types too. (I will say I don't think
> things that mandate an exact number of elements (like point, box, etc) should
> support extra delimiters).
I'm pretty strongly against this, as it would create cross-version hazards
for data. Having queries that depend on newer-version SQL features is
something that people are used to coping with ... but data that loads into
some versions and not others seems like a hassle we do not need to invent.
(Of course, I'm not for the feature w.r.t. SQL either. But breaking data
compatibility is just adding an entire new dimension of trouble.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
