diff options
| author | Bruce Momjian <bruce@momjian.us> | 2016-06-28 14:21:43 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2016-06-28 14:21:43 -0400 |
| commit | 69769a3a6e7c09270aba3094d3ff6df771adf977 (patch) | |
| tree | 953ea3b170243983d156196de731725a9ad83dd5 | |
| parent | 675684fc23fd4287966694b1f108846bc14b6895 (diff) | |
| download | postgresql-69769a3a6e7c09270aba3094d3ff6df771adf977.tar.gz postgresql-69769a3a6e7c09270aba3094d3ff6df771adf977.zip | |
doc: in binary mode mention, say "encoding conversion"
Used to say "character set conversion"
Reported-by: Tatsuo Ishii
Discussion: 20160618.210417.343199294611427151.t-ishii@sraoss.co.jp
| -rw-r--r-- | doc/src/sgml/datatype.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 11e246fa351..9643746ca4a 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -4219,7 +4219,7 @@ SET xmloption TO { DOCUMENT | CONTENT }; <para> When using binary mode to pass query parameters to the server - and query results back to the client, no character set conversion + and query results back to the client, no encoding conversion is performed, so the situation is different. In this case, an encoding declaration in the XML data will be observed, and if it is absent, the data will be assumed to be in UTF-8 (as required by |