Re: additional json functionality - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: additional json functionality
Date
Msg-id m261rq4rz0.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: additional json functionality  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: additional json functionality  (Hannu Krosing <hannu@2ndQuadrant.com>)
Re: additional json functionality  ("David E. Wheeler" <david@justatheory.com>)
Re: additional json functionality  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
"David E. Wheeler" <david@justatheory.com> writes:
> You know that both types support scalar values right? 'a'::JSON works now,
> and 'a'::hstore works with the WIP patch. For that reason I would not think
> that "doc" or "obj" would be good choices.

I'm wondering about just pushing hstore in core (even if technically
still an extension, install it by default, like we do for PLpgSQL), and
calling it a day.

If you need pre-9.4 JSON-is-text compatibility, use the json datatype,
if you want something with general index support, use hstore.

For bikeshedding purposes, what about calling it jstore, as in “we
actually know how to store your json documents”?

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: information schema parameter_default implementation
Next
From: Hannu Krosing
Date:
Subject: Re: additional json functionality