Re: pgxml & xpath_table

From: John Gray <jgray(at)azuli(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: philippe(dot)lang(at)attiksystem(dot)ch, pgsql-general(at)postgresql(dot)org
Subject: Re: pgxml & xpath_table
Date: 2006-06-10 20:10:12
Message-ID: 1149970212.16777.5.camel@adzuki.azuli.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

On Sat, 2006-06-10 at 14:06 -0400, Tom Lane wrote:
> John Gray <jgray(at)azuli(dot)co(dot)uk> writes:
> > This is the reason why xpath_table allows you to specify an
> > identifying field (usually a primary key but doesn't have to be)- the
> > solution to your question is to join an xpath_table that just fetches the
> > document number against the primary key, e.g.:
>
> John, do you think anything could be done in the pgxml documentation to
> make this usage pattern clearer?
>

Yes - I'll write a doc patch for this and include an example like this
by way of demonstration - I notice now that this particular feature
(which I went to some lengths to incorporate in the code!) is completely
undocumented. I'll also consider whether another function with different
behaviour in this situation is possible or helpful.

Give me a few days...

Regards

John

> regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message A. Kretschmer 2006-06-10 20:29:00 Re: Logging and Viewing SQL History
Previous Message Adam 2006-06-10 19:09:36 Logging and Viewing SQL History

Browse pgsql-patches by date

  From Date Subject
Next Message Hannu Krosing 2006-06-11 17:19:37 Re: [PATCHES] ADD/DROP INHERITS
Previous Message Greg Stark 2006-06-10 18:15:18 Re: [PATCHES] ADD/DROP INHERITS