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:29 -0500 |
commit | 75c8ef5ae56c5d9fad594b65eaa3bb8024f7f24f (patch) | |
tree | 9886c769b4b280d939c1aabfe4130b41c5dc4930 /src/fe_utils/conditional.c | |
parent | b6efd8a6daa54b3f94af83767aeaaaeff7c27879 (diff) | |
download | postgresql-75c8ef5ae56c5d9fad594b65eaa3bb8024f7f24f.tar.gz postgresql-75c8ef5ae56c5d9fad594b65eaa3bb8024f7f24f.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/fe_utils/conditional.c')
0 files changed, 0 insertions, 0 deletions