aboutsummaryrefslogtreecommitdiff
path: root/src/backend/libpq/auth.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-08-09 16:35:29 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-08-09 16:35:29 -0400
commit495cadda5ed55f63db9a91d174b6fad0e1816204 (patch)
tree995668755616c0af93c5d8176acc27c0a36016d0 /src/backend/libpq/auth.c
parent9da86753735ab89b0ee685aea985b25c4218ca0b (diff)
downloadpostgresql-495cadda5ed55f63db9a91d174b6fad0e1816204.tar.gz
postgresql-495cadda5ed55f63db9a91d174b6fad0e1816204.zip
Further cleanup of JSON-specific error messages.
Fix an obvious typo in json_build_object()'s complaint about invalid number of arguments, and make the errhint a bit more sensible too. Per discussion about how to word the improved hint, change the few places in the documentation that refer to JSON object field names as "names" to say "keys" instead, since that's what we've said in the vast majority of places in the docs. Arguably "name" is more correct, since that's the terminology used in RFC 7159; but we're stuck with "key" in view of the naming of json_object_keys() so let's at least be self-consistent. I adjusted a few code comments to match this as well, and failed to resist the temptation to clean up some odd whitespace choices in the same area, as well as a useless duplicate PG_ARGISNULL() check. There's still quite a bit of code that uses the phrase "field name" in non-user- visible ways, so I left those usages alone.
Diffstat (limited to 'src/backend/libpq/auth.c')
0 files changed, 0 insertions, 0 deletions