| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-18 01:49:18 |
| Message-ID: | 5289721E.1070109@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Now, if it turns out that the new hstore is not dealing with json input
> and output, we could have json, jstore and hstore.
Jstore isn't the worst name suggestion I've heard on this thread. The
reason I prefer JSONB though, is that a new user looking for a place to
put JSON data will clearly realize that JSON and JSONB are alternatives
and related in some way. They won't necessarily expect that "jstore"
has anything to do with JSON, especially when there is another type
called "JSON". Quite a few people are liable to think it's something to
do with Java.
Besides, we might get sued by these people: http://www.jstor.org/ ;-)
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2013-11-18 01:51:56 | Re: additional json functionality |
| Previous Message | Andrew Dunstan | 2013-11-17 23:20:45 | Re: additional json functionality |