dflorescu at me.com
Sat Oct 10 03:03:35 PDT 2015
The story is more complicated here.
The professor at Irvine Univ. in charge of the students team who designed AsterixDB, Mike Carey, is
today the Chief Architect of CouchDB, who ships the N1QL that I just sent yesterday.
Mike Carey knows exactly XQuery, given that he was in charge of my XQuery processor at BEA Systems after I left.
So it’s definitely not by lack of knowledge that he went BACKWARDS and N1QL is even more primitive then SQL 92
(just added some primitive forms of path expressions to it..)
It’s probably market pressure….
IT HAS TO LOOK LIKE SQL, AND IT HAS TO USE THE THREE MAGIC KEYWORDS “select” “from” AND “where”.
Other then that, who cares that from a data processing perspective, we go backwards where we were in 1994 !???
(and nested select-from-where in the from clause are considered “disruptive” ..huh..)
Are users so ignorant and they prefer a vanilla syntax that they know over significant expressive power ?
> On Oct 9, 2015, at 3:31 PM, Andy Bunce <bunce.andy at gmail.com> wrote:
> Not tried it myself but, AsterixDB  may be of interest to XQuery users.
> >The heart of AQL is the FLWOR (for-let-where-orderby-return) expression. The roots of this expression were borrowed from the expression of the same name in XQuery.
> >but XQuery was co-designed by a diverse band of experienced language designers (SQL, functional programming,and XML experts)
> >and we wanted to avoid revisiting many of the same issues 
>  https://asterixdb.ics.uci.edu/ <https://asterixdb.ics.uci.edu/>
>  https://asterixdb.ics.uci.edu/documentation/aql/manual.html <https://asterixdb.ics.uci.edu/documentation/aql/manual.html>
>  http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf <http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf>
> talk at x-query.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk