Re: Does Type Have = Operator? - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Does Type Have = Operator?
Date
Msg-id AD1CA583-BC8E-42E5-AAC7-173E0E82507C@justatheory.com
Whole thread Raw
In response to Re: Does Type Have = Operator?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Does Type Have = Operator?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On May 12, 2016, at 12:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Andrew mentions in the extension you pointed to that providing a default
> comparison operator would enable people to do UNION, DISTINCT, etc on JSON
> columns without thinking about it.  I'm not convinced that "without
> thinking about it" is a good thing here.  But if we were going to enable
> that, I'd feel better about making it default to jsonb semantics ...

If you want the JSONB semantics, why wouldn’t you use JSONB instead of JSON?

Best,

David


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: alter table alter column ... (larger type) ... when there are dependent views
Next
From: Tom Lane
Date:
Subject: Keeping CURRENT_DATE and similar constructs in original format