[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: The limitations of XPath and navigation for XML database p

• From: "Michael Kay" <mike@s...>
• To: "'Ken North'" <kennorth@s...>,<xml-dev@l...>
• Date: Thu, 7 Feb 2008 09:55:55 -0000

> platform where there was an SQL engine and query optimizer. 
> Declarative (non-procedural) is the alternative to 
> navigational or positional logic.

It's a great mistake to equate navigational with procedural, which is the
trap this article falls into.

Navigational means finding records by virtue of their relationships with
other records, as opposed to content-based retrieval which finds records by
their content alone.

Procedural means giving a sequence of instructions to be followed in order,
typically maintaining state as you go, as opposed to declarative which
describes the output as a pure function of the input.

XPath is navigational but it is not procedural.

It's procedural logic that makes languages hard to optimize, not
navigational logic. XPath is eminently optimizable. As proof of the pudding,
different XML database engines adopt radically different strategies for
evaluating the same XPath expression.


Michael Kay
http://www.saxonica.com/

• References:
  • SQL instead of XQuery
    • From: Dmitry Turin <dev3os@n...>
  • Re: SQL instead of XQuery
    • From: "Andrzej Jan Taramina" <andrzej@c...>
  • The limitations of XPath and navigation for XML database processing
    • From: "Ken North" <kennorth@s...>
  • RE: The limitations of XPath and navigation for XML database processing
    • From: "Michael Kay" <mike@s...>
  • The limitations of XPath and navigation for XML database processing
    • From: "Ken North" <kennorth@s...>