|
23 | 23 |
|
24 | 24 | <para> |
25 | 25 | <productname>PostgreSQL</productname> offers two types for storing JSON |
26 | | - data: <type>json</type> and <type>jsonb</type>. To implementeffective query |
| 26 | + data: <type>json</type> and <type>jsonb</type>. To implementefficient query |
27 | 27 | mechanisms for these data types, <productname>PostgreSQL</productname> |
28 | 28 | also provides the <type>jsonpath</type> data type described in |
29 | 29 | <xref linkend="datatype-jsonpath"/>. |
@@ -233,7 +233,7 @@ SELECT '{"reading": 1.230e-5}'::json, '{"reading": 1.230e-5}'::jsonb; |
233 | 233 | </sect2> |
234 | 234 |
|
235 | 235 | <sect2 id="json-doc-design"> |
236 | | - <title>Designing JSON Documents Effectively</title> |
| 236 | + <title>Designing JSON Documents</title> |
237 | 237 | <para> |
238 | 238 | Representing data as JSON can be considerably more flexible than |
239 | 239 | the traditional relational data model, which is compelling in |
@@ -633,7 +633,7 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu |
633 | 633 |
|
634 | 634 | <para> |
635 | 635 | The <type>jsonpath</type> type implements support for the SQL/JSON path language |
636 | | - in <productname>PostgreSQL</productname> toeffectively query JSON data. |
| 636 | + in <productname>PostgreSQL</productname> toefficiently query JSON data. |
637 | 637 | It provides a binary representation of the parsed SQL/JSON path |
638 | 638 | expression that specifies the items to be retrieved by the path |
639 | 639 | engine from the JSON data for further processing with the |
|