| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Ashoke <s(dot)ashoke(at)gmail(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Postgresql XML parsing |
| Date: | 2014-03-13 16:04:28 |
| Message-ID: | 5321D70C.2030703@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/13/2014 11:27 AM, Ashoke wrote:
> Hi,
>
> Thanks for the input. I would look into JSON parsing as well, but
> the requirement is XML parsing.
>
> There is no DTD/Schema for the XML. Is there any way I could know
> what are the possible tags and their values? I am building my parser
> based on the output PostgreSQL produces (hard coding the tags) and I
> am afraid I would miss out on tags.
>
No, it's not possible, since modules can hook in and add their own nodes
with arbitrary names (see for example the Postgres FDW which does this).
You need to be able to handle arbitrary tags, even if it's by ignoring them.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-13 16:11:23 | Re: [PATCH] Store Extension Options |
| Previous Message | Rajashree Mandaogane | 2014-03-13 15:54:55 | Proposal to join the hackers list |