It may produce the same end result, but it doesn't achieve my goal. Pushing linking into the XQuery layer, to me at least, defeats the whole point of having linking in the first place. I want to be able to use it to simplify and speed up queries, not make them more complex
The user doesn't have to see or interact with the query. The way I see it working is that you perform a standard retrieval through an expander, and the XQuery is used to expand the links. Really, the same functionality could be performed with XSLT, just figured if we were gonna XQuery close to the database, we might as well use that instead.
If there is runtime cost in converting DOM impls then it seems that would be an optimization point for the developer to worry about as part of the price for embedding the server. Anyway, I'm obviously unclear on the details here, I thought our DOM would always have this problem because of the compression system?
When I implement the DTSM stuff, I'm going to layer the compression system deeper and expose it using the DTM so that we can layer SAX or DOM on top of that.
Oh come on, let's be realistic here. XQuery is far closer to being complete then XUpdate. You know perfectly well that there is an update syntax that exists and has even been implemented a couple times. http://www.lehti.de/beruf/diplomarbeit.pdf Regardless of whether or not it is stable or part of XQuery 1.0 the language is still far more complete. XUpdate it self isn't even complete and the query component required doesn'
t even exist. XSelect is at a far less mature status then the update extensions for XQuery. Additionally XUpdate was never intended to be more then a stop-gap while XQuery was developed. I hate to defend XQuery, but we have to at least keep one foot grounded in reality.
Dude, how long have you been working with me that you still don't know when I'm talking out of my ass? If we can get XQuery implemented and its not a quickly moving target, I can wait for updates. Maybe we can implement UpdateGrams :-)
-- Tom Bradford - http://www.tbradford.org Developer - Apache Xindice (Native XML Database) Creator - Project Labrador (Web Services Framework)
