| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-17 21:51:31 |
| Message-ID: | m261rq4rz0.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)justatheory(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2013-11-17 22:01:27 | Re: additional json functionality |
| Previous Message | Tom Lane | 2013-11-17 21:38:45 | Re: information schema parameter_default implementation |