aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-09-26 21:27:34 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-09-26 21:29:31 +0200
commit6c3ef7482f2bdedc68146a4ffcba4b8b241b91a9 (patch)
treed5ab52f29ce1b1b291cb5f52912de738cc9dbaf0
parenta4a5c0cf9cec3df2d1662a799c539c2cc84aa463 (diff)
downloadpostgresql-6c3ef7482f2bdedc68146a4ffcba4b8b241b91a9.tar.gz
postgresql-6c3ef7482f2bdedc68146a4ffcba4b8b241b91a9.zip
doc: Format example JSON data better
-rw-r--r--doc/src/sgml/func.sgml15
1 files changed, 9 insertions, 6 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index cc3041f6373..5b2c87705ef 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -12916,17 +12916,20 @@ table2-mapping
For example, suppose you have some JSON data from a GPS tracker that you
would like to parse, such as:
<programlisting>
-{ "track" :
- {
- "segments" : [
- { "location": [ 47.763, 13.4034 ],
+{
+ "track": {
+ "segments": [
+ {
+ "location": [ 47.763, 13.4034 ],
"start time": "2018-10-14 10:05:14",
"HR": 73
},
- { "location": [ 47.706, 13.2635 ],
+ {
+ "location": [ 47.706, 13.2635 ],
"start time": "2018-10-14 10:39:21",
"HR": 135
- } ]
+ }
+ ]
}
}
</programlisting>