|
[XQuery Talk Mailing List Archive Home] [By Date] [By Thread] [By Subject] [By Author] [Recent Entries] [Reply To This Message] [Announce] XQilla version 1.1.0 releasedAndrew Welch andrew.j.welch at gmail.comTue Sep 4 14:40:36 PDT 2007
On 9/4/07, John Snelson <http://x-query.com/mailman/listinfo/talk> wrote: > Andrew Welch wrote: > > On 9/4/07, John Snelson <http://x-query.com/mailman/listinfo/talk> wrote: > > > > The point I was trying to make was that XQuery + XML DB should be able > > to select nodes far faster than XSLT + REST API, so the ideal > > combination is XSLT + XQuery extension function. > > Surely what you really want is an XSLT processor in the XML database? That would be ideal... as long as XSLT is susceptible to all of the optimisations that XQuery is. (which I don't think it is) > > xmldb($db-uri, $collection, $xpath) > > > > and returned a sequence then that would do the job... > > Right - that would be the other way to do it. If you want your XSLT to > be executed by the database client, you can just make calls into the XML > database from the XSLT. This approach would give less scope for the > database to optimise the XSLT using it's indexes though. ...which is why I was thinking just pass an XQuery to the XML database so that the XQuery engine can do what it does well, and then process the entire result set with a single XSLT. -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

![[Announce] XQilla version 1.1.0 released](/images/get_stylus.gif)




