| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Avoid undesired flattening of jsonb arrays? |
| Date: | 2020-12-18 16:20:34 |
| Message-ID: | 160622.1608308434@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> I'll agree that the description could discuss the case explicitly, and the
> array||scalar case could be added to the examples.
Yeah, the documentation completely fails to explain what happens
when the inputs aren't two arrays or two objects. I'd kind of assumed
that that's an error, but it isn't. Some experimentation indicates
that the behavior in all cases except two objects is to convert any
non-array input to a one-element array, reducing the situation to the
two-array case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2020-12-18 17:03:16 | Re: Avoid undesired flattening of jsonb arrays? |
| Previous Message | Lars Vonk | 2020-12-18 15:42:12 | Missing rows after migrating from postgres 11 to 12 with logical replication |