| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb contains behaviour weirdness |
| Date: | 2014-09-15 17:08:28 |
| Message-ID: | 54171D0C.8070802@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/12/2014 01:33 PM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> However, this better become a FAQ item, because it's not necessarily the
>> behavior that folks used to JSON but not Postgres will expect.
>
> No, it's a bug, not a documentation deficiency.
Hmmm? Are you proposing that we should change how ARRAY @> ARRAY works
for non-JSON data?
Or are you proposing that JSONARRAY @> JSONARRAY should work differently
from ARRAY @> ARRAY?
Or are you agreeing with Peter that it's the first case that's a bug,
and the 2nd two tests are correct, and just being unclear?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-09-15 17:12:18 | Re: jsonb format is pessimal for toast compression |
| Previous Message | Robert Haas | 2014-09-15 16:41:25 | Re: Postgres code for a query intermediate dataset |