diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2019-09-08 11:10:49 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2019-09-08 11:11:24 +0200 |
| commit | 422910423b6cba6abc3790b8f20854c9e78e04a4 (patch) | |
| tree | c24936d476436f78482eb26f24da1de30b09de88 /doc/src | |
| parent | eecd7c3d2b44094d00e967c7283fc2236d8def5d (diff) | |
doc: effective -> efficient
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/json.sgml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index cf50410d406..2d2f404b73e 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -23,7 +23,7 @@ <para> <productname>PostgreSQL</productname> offers two types for storing JSON - data: <type>json</type> and <type>jsonb</type>. To implement effective query + data: <type>json</type> and <type>jsonb</type>. To implement efficient query mechanisms for these data types, <productname>PostgreSQL</productname> also provides the <type>jsonpath</type> data type described in <xref linkend="datatype-jsonpath"/>. @@ -233,7 +233,7 @@ SELECT '{"reading": 1.230e-5}'::json, '{"reading": 1.230e-5}'::jsonb; </sect2> <sect2 id="json-doc-design"> - <title>Designing JSON Documents Effectively</title> + <title>Designing JSON Documents</title> <para> Representing data as JSON can be considerably more flexible than the traditional relational data model, which is compelling in @@ -633,7 +633,7 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu <para> The <type>jsonpath</type> type implements support for the SQL/JSON path language - in <productname>PostgreSQL</productname> to effectively query JSON data. + in <productname>PostgreSQL</productname> to efficiently query JSON data. It provides a binary representation of the parsed SQL/JSON path expression that specifies the items to be retrieved by the path engine from the JSON data for further processing with the |