diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-12-21 13:11:29 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-12-21 13:11:51 -0500 |
commit | 38d30a14b05e0cc2996fd311d94d7ae4fe2122aa (patch) | |
tree | 3a787da72cf33fea05dd58fe9dae02e5dab359c5 /src/backend/executor/execProcnode.c | |
parent | be9c3cd186ba86b9bc3df7ecc64b81ce4726810d (diff) | |
download | postgresql-38d30a14b05e0cc2996fd311d94d7ae4fe2122aa.tar.gz postgresql-38d30a14b05e0cc2996fd311d94d7ae4fe2122aa.zip |
Remove "invalid concatenation of jsonb objects" error case.
The jsonb || jsonb operator arbitrarily rejected certain combinations
of scalar and non-scalar inputs, while being willing to concatenate
other combinations. This was of course quite undocumented. Rather
than trying to document it, let's just remove the restriction,
creating a uniform rule that unless we are handling an object-to-object
concatenation, non-array inputs are converted to one-element arrays,
resulting in an array-to-array concatenation. (This does not change
the behavior for any case that didn't throw an error before.)
Per complaint from Joel Jacobson. Back-patch to all supported branches.
Discussion: https://postgr.es/m/163099.1608312033@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/execProcnode.c')
0 files changed, 0 insertions, 0 deletions