RE: implementing XPath over a DB like DB2

Software AG's XML database, Tamino, has a query language which is
essentially an extended XPath; the implementation can take advantages of
indexes to optimize the query and search gigabytes of persistent data. The
new XQuery specification is a superset of XPath so the same technology is
needed.

The model is not that the database is one huge XML document, rather it is a
collection of documents, and one of the extensions to XPath semantics is the
extension to apply a single XPath expression to such a collection.

We have an XSLT processor inside Tamino that's designed to achieve close
integration with the database, though as yet it is not operating directly on
the persistent data: it operates on documents that you create as the result
of a query.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Russell
> Balest
> Sent: 13 March 2002 16:20
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  implementing XPath over a DB like DB2
>
>
>
>
>     In the Xalan-J 2.0 design documentation, there is a section called
> XPath Database Connection ( you should check it out, it has a
> very nice
> picture).    They describe implementing the NodeIterator
> interface on top of a
> database like DB2.   ( see
> http://xml.apache.org/xalan-j/design/design2_0_0.html#xpathdbconn  )
>     My conception of this is an XML _document_ that lives in
> a database
> (because it's many Gbytes), but you can
> still apply XSLT to it, transparently.
>     Has anyone done this or know of examples.
> Alternatively,  is anyone doing
> any XSLT on XML that lives in
> a DB - not a file.   How do you do it?
>
>    Russell Balest
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list