提交 b92767d5 编写于 作者: B Bruce Momjian

Update "encode" documentation to mention that 'escape' only changes null

bytes and backslashes, remove "ASCII" mention.  Backpatch to 8.2.X.
上级 298de77d
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.368 2007/02/20 18:18:05 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.369 2007/02/20 19:59:04 momjian Exp $ -->
<chapter id="functions"> <chapter id="functions">
<title>Functions and Operators</title> <title>Functions and Operators</title>
...@@ -1356,8 +1356,10 @@ ...@@ -1356,8 +1356,10 @@
</entry> </entry>
<entry><type>text</type></entry> <entry><type>text</type></entry>
<entry> <entry>
Encode binary data to <acronym>ASCII</acronym>-only representation. Supported Encode binary data to different representation. Supported
types are: <literal>base64</>, <literal>hex</>, <literal>escape</>. types are: <literal>base64</>, <literal>hex</>, <literal>escape</>.
<literal>Escape</> merely outputs null bytes as <literal>\000</> and
doubles backslashes.
</entry> </entry>
<entry><literal>encode( E'123\\000\\001', 'base64')</literal></entry> <entry><literal>encode( E'123\\000\\001', 'base64')</literal></entry>
<entry><literal>MTIzAAE=</literal></entry> <entry><literal>MTIzAAE=</literal></entry>
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册