| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-28 04:21:30 |
| Message-ID: | 53100ECA.1090307@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/27/2014 05:54 PM, Josh Berkus wrote:
>
>
> And it's not just that "broadly speaking most people would prefer
> the interface to speak JSON"; it's that a JSONish interface for indexed
> heirachical data is a Big Feature which will drive adoption among web
> developers, and hstore2 without JSON support simply is not. At trade
> shows and developer conferences, I get more questions about PostgreSQL's
> JSON support than I do for any new feature since streaming replication.
>
Just to back this up. This is not anecdotal. I have multiple customers
performing very large development projects right now. Every single one
of them is interested in the pros/cons of using PostgreSQL and JSON.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2014-02-28 04:23:51 | Re: jsonb and nested hstore |
| Previous Message | Peter Geoghegan | 2014-02-28 04:08:09 | Re: jsonb and nested hstore |