| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | fabriziomello(at)gmail(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Does Type Have = Operator? |
| Date: | 2016-05-12 21:25:56 |
| Message-ID: | AD1CA583-BC8E-42E5-AAC7-173E0E82507C@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 12, 2016, at 12:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-12 22:14:54 | Keeping CURRENT_DATE and similar constructs in original format |
| Previous Message | Tom Lane | 2016-05-12 19:15:41 | Re: alter table alter column ... (larger type) ... when there are dependent views |