summaryrefslogtreecommitdiff
path: root/src/include/utils/memutils.h
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-06-29 13:50:58 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-06-29 13:50:58 -0400
commita749a23d7af4dba9b3468076ec561d2cbf69af09 (patch)
treea2e0ebac0a075c5004156a2ca5b96272f0827ae6 /src/include/utils/memutils.h
parent51adcaa0df81da5e94b582d47de64ebb17129937 (diff)
downloadpostgresql-a749a23d7af4dba9b3468076ec561d2cbf69af09.tar.gz
Remove use_json_as_text options from json_to_record/json_populate_record.
The "false" case was really quite useless since all it did was to throw an error; a definition not helped in the least by making it the default. Instead let's just have the "true" case, which emits nested objects and arrays in JSON syntax. We might later want to provide the ability to emit sub-objects in Postgres record or array syntax, but we'd be best off to drive that off a check of the target field datatype, not a separate argument. For the functions newly added in 9.4, we can just remove the flag arguments outright. We can't do that for json_populate_record[set], which already existed in 9.3, but we can ignore the argument and always behave as if it were "true". It helps that the flag arguments were optional and not documented in any useful fashion anyway.
Diffstat (limited to 'src/include/utils/memutils.h')
0 files changed, 0 insertions, 0 deletions