On 3/6/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
On 3/6/07, Mike Rylander <[EMAIL PROTECTED]> wrote:
> Attatched you'll find a patch that I've been kicking around for a
> while that I'd like to propose for inclusion in 8.3.  I attempted to
> submit this through the original xml2 author (as far back as the  7.4
> days) but got no response.
> It's really fairly trivial, but I will be using the features it
> provides in production soon, so I'd like to see it applied against the
> contrib xml2 module.  The patch adds support for default XML
> namespaces in xml2 by providing a mechanism for supplying a prefix to
> a named namespace URI.  It then wraps the namespace-capable functions
> in backward-compatible equivalents so that old code will not break.

1) And what about non-default namespaces?

I'm not sure I understand.  If the namespace already has a prefix then
it works fine.  This patch simply gives a known non-prefixed namespace
URI a prefix so one can write XPath that looks like

 //marc:[EMAIL PROTECTED]'245']/marc:[EMAIL PROTECTED]'a']

instead of

 //*[local-name()='datafield' and
@tag='245']/*[local-name()='subfied' and @code='a']

A little two node example is painful enough, now imagine a non-trivial
example with backtracking conditionals... :P

2) What if my XPath query has different prefix, that also should be
mapped to the same URI? (Not frequent case, but this really can occur
-- e.g. XML doc has prefix 'local' for URI='', but
XPath should have 'loc' for the same URI.)

Both prefixes work fine as multiple prefixes can map to the same URI.

Best regards,

Mike Rylander
GPLS -- PINES Development
Database Developer

---------------------------(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

Reply via email to