It's also worth to take care of the very last lines of XML functions
"XML to SQL Mapping
This involves converting XML data to and from relational
structures. PostgreSQL has no internal support for such mapping, and
relies on external tools to do such conversions."
It's not quite rigth as of now, because "rel->XML" mapping
capabilities exist in the core: it's XML/SQL publishing functions and
alternative mapping functions (such as table_to_xml() ).
On 4/10/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Here is new version that adds following changes:
4. Function is now strict, per discussion.
5. Return empty array in case when XPath expression detects nothing
(previously, NULL was returned in such case), per discussion.
6. (bugfix) Work with fragments with prologue: select xpath('/a',
'<?xml version="1.0"?><a /><b />'); // now XML datum is always wrapped
with dummy <x>...</x>, XML prologue simply goes away (if any).
7. Some cleanup.
On 4/4/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
> The patch attached contains following changes:
> 1. The function name xmlpath() is changed to xpath();
> 2. Approach of passing of namepspace mappings to the function is changed:
> now that array (the 3rd argument) should be a 2-dimentional array with the
> length of the second axis = 2 (e.g., ARRAY[ARRAY['a1', 'http://a1'],
> ARRAY['a2', 'http://a2'], ARRAY['a2', 'http://a2']]);
> 3. Description of xpath() function in docs (I'm sorry for possible
> mistakes in English and docbook formatting, please check it...)
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster