May I ask a question about this?
I will be working on an older database in which the original developer
stored XML documents as a single variable length text field. To process it,
it has to be retrieved in full and parsed. But the structure of it is
simple in that it has an element for each field in the DB that replaced the
earily version. But people are still using the earlier one because they
still need access to the old data and no tool has yet been written by my
predecessors to move the old data over to the new DB. Does the XML support
you're all talking about make it less tedious to develop tools to parse
these old XML files and put their data into the right field of the right
table? I can develop the tool our users need using the resources I have at
hand, but the proces of parsing these XML files is certain to be very
tedious; something I am not looking forward to. There is a reason I don't
do much with XML even though I know how.
Ted
----- Original Message -----
From: "Steve Atkins" <steve@blighty.com>
To: "pgsql general" <pgsql-general@postgresql.org>
Sent: Wednesday, March 29, 2006 12:21 PM
Subject: Re: [GENERAL] PostgreSQL's XML support comparison against other
RDBMSes
>
> On Mar 29, 2006, at 2:57 AM, Ivan Zolotukhin wrote:
>
>> On 3/29/06, Peter Eisentraut <peter_e@gmx.net> wrote:
>>> Ivan Zolotukhin wrote:
>>>> BTW, are there any plans for its improvement? What are the first
>>>> steps for the people who want to contribute to PostgreSQL in this
>>>> field?
>>>
>>> The first step would be making a detailed analysis of what "XML
>>> support"
>>> is supposed to mean.
>>
>> So let's make such analysis here within PostgreSQL community! There
>> were a lot of talks about XML support in Postgres, but they did not
>> lead to any steady work in this direction. IMHO, it's time to start it
>> now, no?
>
> The people who want it should explain what it is, ideally by
> pointing at the relevant standards documents.
>
> Cheers,
> Steve
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>