diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2007-01-19 16:58:46 +0000 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2007-01-19 16:58:46 +0000 |
| commit | 4b48ad4fb2edf897b87d04467f8eaaaba82a258f (patch) | |
| tree | ba5d42f78007a28afcb0f18adae57243c6559fb1 /doc/src | |
| parent | 5b4a08896bd6ee7d93f74c77f61d3518deda8fd5 (diff) | |
| download | postgresql-4b48ad4fb2edf897b87d04467f8eaaaba82a258f.tar.gz postgresql-4b48ad4fb2edf897b87d04467f8eaaaba82a258f.zip | |
Add support for converting binary values (i.e. bytea) into xml values,
with new GUC parameter "xmlbinary" that controls the output encoding, as
per SQL/XML standard.
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 29 |
1 files changed, 28 insertions, 1 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index ef809027476..2c697152e0a 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.102 2007/01/16 18:26:02 alvherre Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.103 2007/01/19 16:58:45 petere Exp $ --> <chapter Id="runtime-config"> <title>Server Configuration</title> @@ -3502,6 +3502,33 @@ SELECT * FROM parent WHERE key = 2400; </listitem> </varlistentry> + <varlistentry id="guc-xmlbinary" xreflabel="xmlbinary"> + <term><varname>xmlbinary</varname> (<type>string</type>)</term> + <indexterm> + <primary><varname>xmlbinary</> configuration parameter</primary> + </indexterm> + <listitem> + <para> + Sets how binary values are to be encoded in XML. This applies + for example when <type>bytea</type> values are converted to + XML by the functions <function>xmlelement</function> or + <function>xmlforest</function>. Possible values are + <literal>base64</literal> and <literal>hex</literal>, which + are both defined in the XML Schema standard. The default is + <literal>base64</literal>. For further information about + XML-related functions, see <xref linkend="functions-xml">. + </para> + + <para> + The actual choice here is mostly a matter of taste, + constrained only by possible restrictions in client + applications. Both methods support all possible values, + although the hex encoding will be somewhat larger than the + base64 encoding. + </para> + </listitem> + </varlistentry> + </variablelist> </sect2> <sect2 id="runtime-config-client-format"> |