From 4b48ad4fb2edf897b87d04467f8eaaaba82a258f Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 19 Jan 2007 16:58:46 +0000 Subject: 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. --- doc/src/sgml/config.sgml | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) (limited to 'doc/src') 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 @@ - + Server Configuration @@ -3502,6 +3502,33 @@ SELECT * FROM parent WHERE key = 2400; + + xmlbinary (string) + + xmlbinary configuration parameter + + + + Sets how binary values are to be encoded in XML. This applies + for example when bytea values are converted to + XML by the functions xmlelement or + xmlforest. Possible values are + base64 and hex, which + are both defined in the XML Schema standard. The default is + base64. For further information about + XML-related functions, see . + + + + 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. + + + + -- cgit v1.2.3