diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-12-21 13:11:30 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-12-21 13:11:30 -0500 |
commit | 1d5f3f976b26271b51a619f02436ec5c263db9f3 (patch) | |
tree | 4f47c7cb0a95d9b308a9006a2e009a5358d1f872 /src/tutorial/complex.c | |
parent | c336e90b266bb92a7c782eaefbeb038522e41c4b (diff) | |
download | postgresql-1d5f3f976b26271b51a619f02436ec5c263db9f3.tar.gz |
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/tutorial/complex.c')
0 files changed, 0 insertions, 0 deletions