From: | Nathan Widmyer <lighthousej(at)gmail(dot)com> |
---|---|
To: | Scott Bailey <artacus(at)comcast(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Current state of XML capabilities in PostgreSQL? |
Date: | 2009-09-16 22:58:39 |
Message-ID: | db4f7fd10909161558w4d2487c0p5094e76284247ae8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have this XML that I don't wish to parse out to tables (BTDT and
don't wish to go there for the most part). There might be the
uncommon chance where an XML-friendly operation would be very useful.
On 9/16/09, Scott Bailey <artacus(at)comcast(dot)net> wrote:
>> I'm looking for the current state of XML capabilities in PostgreSQL and
>> I'm coming up with a lot of confusing links and a bit short on
>> documentation.
>
>
> Postgres' XML is still lacking in a few spots. But the core
> functionality is certainly there to do all of the every day stuff.
>
> The trick with working with XML in the database is to know when to store
> it as XML and when to shred it into relational tables. If its a
> structured document (looks like something you'd open in Word) save it as
> XML. If it looks like something you'd open in Excel then start
> shredding. And it looks like maybe you want to do a tv guide type thing.
> That is something you'll want to shred to tables.
>
>> I'm looking for the functionality that I mentioned above that allowed
>> more comprehensive XML operations but I'm just not finding any
>> documentation for it, if it exists.
>
> What exactly is it you are trying to do but cant?
>
> Scott
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-09-16 23:01:40 | Re: Unicode normalization |
Previous Message | sulmansarwar | 2009-09-16 22:56:15 | Segmentation fault during restoration of compressed(.gz) database |