> Part of the answer, I think, is to make performance less reliant on good > optimization. In XSLT , the key() function goes a long way towards this: > by giving programmers a tool to control when indexes are built and used, > performance of many join constructs becomes much more predictable > > I’ve always felt that the anathema felt > in the database query community towards such constructs is misplaced – > alhough it’s great when optimizers are good enough that they aren’t needed, > I’ve seen programmers tearing their hair out trying to second-guess the > optimizer, and in such cases it’s not clear we’re doing programmers a > service. This is indeed somewhat funny.

See the original post:
Requirements on Optimizers [was ANSWERS to "What's
wrong with XQuery" question]

On 7/25/2010 9:51 AM, Martin Probst wrote: > > Part of the answer, I think, is to make performance less reliant on good > > optimization. In XSLT , the key() function goes a long way towards this: > > by giving programmers a tool to control when indexes are built and used, > > performance of many join constructs becomes much more predictable > > > > > > > It might be nice to have language constructs saying ” guarantee to me > that you do this in O(something), otherwise fail”. > That’s exactly right – for applications with sufficient scale, it’s just not enough to know that a given expression will be evaluated correctly: it’s also critical to understand whether indexed lookup will be applied so as to guarantee completion (or failure) before the universe ends

Read more from the original source:
Requirements on Optimizers [was ANSWERS to "What's
wrong with XQuery" question]

Interesting idea In the java and c++ case the libraries are more implementations then specifications And in particular the collection classes (both Languages) the classes themselves Are architected around separating specific algorithm models from abstract non algorithmic interfaces. I don’t see quite the same thing in either xquery languages or stdlibs However I do see it in implementation extensions Maybe when xquery libs achieve the same maturity as java and c++ libs well start to see algorithmic metrics as part of the docs if not the specs David A Lee On Jul 25, 2010, at 12:10 AM, Pavel Minaev wrote: > Nonetheless it’s fairly common, though typically not in the languages > themselves, but rather libraries.

See the article here:
Requirements on Optimizers

Although we were talking about a lack of interest in XML in the web community, I found it rather heartening to see some good participation in the interest of bringing E4X support to Chrome’s V8 engine (as E4X is already in Firefox), with the intention of getting critical mass to lead to adoption by the other browsers. V8 has indicated in theory their willingness to integrate good code, as long as it is produced by a third-party: http://code.google.com/p/v8/issues/detail?id=235#c19 Several there have already mentioned being willing to donate to try to make it happen, including with the hope that if more browsers besides Mozilla support E4X, there may be potential to see it become standard across browsers

Visit link:
E4X and XQuery

I think if I were writing a library for a vocabulary where schema validation is the norm (like FpML , say), and assuming that the schema is suitable for use in XQuery (most element names either global or having a named complex type) then I would declare the functions with types that assume the data is pre-validated. I wouldn’t expect client code to be invoking validate{} explicitly – I would expect that most of the time, the function is called to operate directly on input data, which is validated at source outside the query. (But that might not be how Zorba works, I don’t know.) The main reason is that it’s a good idea in an interface definition to be as precise as possible about what you expect to cross the interface

See the rest here:
Schema Typed Parameters and Return Values in Library
Modules

On 19/07/2010 00:16, Philip Fennell wrote: > Whilst in the process of generating some XQuery code via XQueryX I’ve noticed that the area of variable declarations ‘xqx:varDecl’ does not seem to be supported properly/completely by the published XML Schema . > > The following example: > > > NAT_ID > > xs:string > ? > > > > > causes the validation to fail (in oXygen using Xerces ) with this message: > > SystemID: C:Users..

See the original post:
I’ve got an issue with the XQueryX Schema…

Released xmlsh version 1.0.7, a command line (and scripting) shell for text and XML processing based on the unix shells but redesigned for today’s modern processing needs.

The rest is here:
ANNOUNCE: xmlsh 1.0.7 with support for Saxon EE,
PE. New function call syntax, other bug fixes.

Hi Paul, Regarding SKOS [1, 2], I’d be happy to try and answer any questions you have. You might also ask on the http://x-query.com/mailman/listinfo/talk mailing list , which is the SKOS community mailing list, and which would also be a good place to ask for recent information on published SKOS data. I’m sorry there is no definitive list of available SKOS data, but two other good places to look for information on published SKOS data are the SKOS implementation report [3] and the SKOS datazone wiki page [4]

The rest is here:
Implementing the XQuery full-text thesaurus match option

There are many ways to export data to SQL Azure. Plain T-SQL INSERT statements, bulk copy utility (bcp.exe) of SQL Server 2008 R2, SQL Azure Migration Wizard and SQL Server Integration Services (SSIS) are some of them. This weekend I wanted to upload…( read more )

Originally posted here:
Exporting Stack Overflow Data to SQL Azure

Your conclusion is: Xquery doesn’t get close to the mature capabilities of relational database systems when it comes to dealing with relational data! Well of course it doesn’t. It’s not designed to do that job . Data is naturally hierarchical, and XQuery is good at processing it in its hierarchical form.

Go here to read the rest:
Article posted on Experts Exchange about XQuery
outer joins