From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-02-25 18:54:28 |
Message-ID: | 530CE6E4.7030102@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02/25/2014 10:50 AM, Robert Haas wrote:
> On Tue, Feb 25, 2014 at 1:45 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> On 02/25/2014 10:31 AM, Robert Haas wrote:
>>> And I definitely don't
>>> agree that our documentation should push people towards stuffing
>>> everything in a JSON blob instead of using real column definitions.
>>
>> ????
>>
>> Where did you get this out of my doc patch?
>
> Way to quote what I said out of context.
Way to put words in my mouth.
> But to make a long story short, I get that from the fact that you want
> to railroad everyone into using jsonb.
That's called a "straw man argument", Robert.
Me: We should recommend that people use jsonb unless they have a
specific reason for using json.
Merlin: We should present them side-by-side with a complex comparison.
Robert: Josh wants to junk all relational data and use only jsonb!
I mean, really, WTF?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2014-02-25 19:07:57 | Re: jsonb and nested hstore |
Previous Message | Robert Haas | 2014-02-25 18:51:12 | Re: Minor comment improvements in tablecmds.c |