Issue: Deprecation of the XML2 module 'xml_is_well_formed' function

From: Mike Berrow <mberrow(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Issue: Deprecation of the XML2 module 'xml_is_well_formed' function
Date: 2010-06-28 15:03:17
Message-ID: AANLkTim8ije1V2-yiK794kGjc-9ZdgW_0wLweYbg5ffS@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

We need to make extensive use of the 'xml_is_well_formed' function provided
by the XML2 module.

Yet the documentation says that the xml2 module will be deprecated since
"XML syntax checking and XPath queries"
is covered by the XML-related functionality based on the SQL/XML standard in
the core server from PostgreSQL 8.3 onwards.

However, the core function XMLPARSE does not provide equivalent
functionality since when it detects an invalid XML document,
it throws an error rather than returning a truth value (which is what we
need and currently have with the 'xml_is_well_formed' function).

For example:

select xml_is_well_formed('<br></br2>');
xml_is_well_formed
--------------------
f
(1 row)

select XMLPARSE( DOCUMENT '<br></br2>' );
ERROR: invalid XML document
DETAIL: Entity: line 1: parser error : expected '>'
<br></br2>
^
Entity: line 1: parser error : Extra content at the end of the document
<br></br2>
^

Is there some way to use the new, core XML functionality to simply return a
truth value
in the way that we need?.

Thanks,
-- Mike Berrow

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike Berrow 2010-06-28 15:08:53 Issue: Deprecation of the XML2 module 'xml_is_well_formed' function
Previous Message Tom Lane 2010-06-28 14:53:24 Re: get_whatever_oid, part 1: object types with unqualifed names