Re: XMLEXISTS on legacy XML with malformed xmlns - Mailing list pgsql-general

From Pavel Stehule
Subject Re: XMLEXISTS on legacy XML with malformed xmlns
Date
Msg-id CAFj8pRAf1Q-SnHZ5LUsXJ2dDDcEv0k0pK8zQAFXYgd89cEeuiA@mail.gmail.com
Whole thread Raw
In response to XMLEXISTS on legacy XML with malformed xmlns  (Edson Richter <edsonrichter@hotmail.com>)
Responses Re: XMLEXISTS on legacy XML with malformed xmlns  (Edson Richter <edsonrichter@hotmail.com>)
List pgsql-general


2016-02-12 1:53 GMT+01:00 Edson Richter <edsonrichter@hotmail.com>:
Hi!

I've some (about 1M records) containing legacy XML I would like to parse and apply XMLEXISTS.

This is the query:

select * from xmllog
 where xpath_exists(('//MyDocument[@DocNum = ''000411828'']'::text), xmlparse(document cdataout));

This is the error:

ERRO: could not parse XML document
SQL state: 2200M
Detail: line 2: xmlns:leg: 'LEGACYAPP - SEND MSG EVENTS ABOUT' is not a valid URI
<leg:sendmsgeventsabout xmlns:leg="LEGACYAPP - SEND MSG EVENTS ABOUT">
^

This is the sample XML with malformed xmlns (I've shortenet the data, but the important thing here is the malformed xmlns):

"<?xml version="1.0" encoding="utf-8" ?>
<leg:sendmsgeventsabout  xmlns:leg="LEGACYAPP - SEND MSG EVENTS ABOUT">
  <carrier xmlns="" controlnum="04503660000146">
    <MyDocument DocNum="000511852">
      <other_info>0</other_info>
      <complement info (...)"


I can easly read this XML in Notepad++, and also in Java - but PostgreSQL always throw error.

Can you plase tell me how can make PostgreSQL ignore this malformed xmlns and proceed processing the XML?

PostgreSQL uses libxml2, but the usage isn't too configurable. So my advice is using defensive strategy and clean/fix wrong namespace with string tools - replace function.

Regards

Pavel
 

Thanks,

--
Atenciosamente,

Edson Carlos Ericksson Richter



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: 9.4 -> 9.5 dump size reduction
Next
From: Albe Laurenz
Date:
Subject: Re: PosgreSQL Security Architecture