From: | Chris Roffler <croffler(at)earthlink(dot)net> |
---|---|
To: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: XML Index again |
Date: | 2010-03-08 12:50:11 |
Message-ID: | 3984722a1003080450k1ce8310asf62f22f8b36514d1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yup you are right .... however I am trying to run benchmarks with the two
solutions.
The xml solution will give us more flexibility in the future , just in case
we do not have attribute/value lists :)
On Mon, Mar 8, 2010 at 1:33 PM, Alban Hertroys <
dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> wrote:
> On 8 Mar 2010, at 11:39, Chris Roffler wrote:
>
> > Alban
> >
> > Thanks for your help, your suggestion worked.
> >
> > I need another xpath expression to find any Attribute with Name ="xxxx"
> under the Attributes node. (not just if it is in a specific position)
> > see query below.
> > How do I create an index for this xpath expression ?
>
> Come to think of it... You seem to be storing an attribute/value list in
> the database in XML. Is there any reason not to store the attributes and
> their values as a normal table? Your approach seems a bit over-complicated
> and you seem to have some trouble getting your own mind around it.
>
> Alban Hertroys
>
> --
> If you can't see the forest for the trees,
> cut the trees and you'll see there is no forest.
>
>
> !DSPAM:1034,4b94e081296926114815748!
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | seiliki | 2010-03-08 12:52:30 | Re: Libpq: copy file to bytea column |
Previous Message | Michał Pawlikowski | 2010-03-08 12:38:14 | Re: ERROR: invalid byte sequence for encoding "UTF8": 0x93 Error |