From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | John Gray <jgray(at)azuli(dot)co(dot)uk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, philippe(dot)lang(at)attiksystem(dot)ch, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgxml & xpath_table |
Date: | 2006-08-22 03:38:25 |
Message-ID: | 200608220338.k7M3cPZ13584@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
John Gray wrote:
> 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...
FYI, I have not seen a patch for this yet.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Vance Maverick | 2006-08-22 04:16:14 | UUID as primary key |
Previous Message | Bruce Momjian | 2006-08-22 03:37:31 | Re: new FAQ entry (was:Re: UTF8 problem) |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-08-22 03:47:25 | Re: SQL/XML publishing function experimental patch |
Previous Message | Bruce Momjian | 2006-08-22 02:54:47 | Re: pgstattuple extension for indexes |