aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/encode.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-12-21 13:11:29 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-12-21 13:11:50 -0500
commitff5d5611c01f60525c30b2c3ebc16d05edb7956d (patch)
treefdba3512f73c4805109f295ad0208846b7fb94ed /src/backend/utils/adt/encode.c
parent86b7cca72d4d0a4e043fac0a2cdd56218ff2f258 (diff)
downloadpostgresql-ff5d5611c01f60525c30b2c3ebc16d05edb7956d.tar.gz
postgresql-ff5d5611c01f60525c30b2c3ebc16d05edb7956d.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/utils/adt/encode.c')
0 files changed, 0 insertions, 0 deletions