From leo.studer at varioweb.ch Tue Oct 6 09:23:32 2015 From: leo.studer at varioweb.ch (Leo Studer) Date: Tue, 6 Oct 2015 18:23:32 +0200 Subject: [xquery-talk] Update bug? Message-ID: Hello I am using Oxygen 17.0 with Saxon EE 9.6.0.5 as the xQuery Update processor. I want to move an attribute one level deeper. In the example I want to move att="att? from to Here my code: delete node doc("xml.xml")//@att, insert node doc("xml.xml")//@att into doc("xml.xml")//b Each of these two statements work correctly alone but when I try both together I get java.lang.NullPointerException. Can anyone explain what happens here? Thanks in advance Leo -------------- next part -------------- An HTML attachment was scrubbed... URL: From joemfb at gmail.com Tue Oct 6 09:54:40 2015 From: joemfb at gmail.com (Joseph Bryan) Date: Tue, 6 Oct 2015 12:54:40 -0400 Subject: [xquery-talk] Update bug? In-Reply-To: References: Message-ID: Hi Leo, Try reversing the order of your statements, first inserting the node as a child of before deleting it. Also, you probably don't want to be using // in your selectors, which means the descendant-or-self axis. With that XPath expression, any @att at any level of the document would be copied and then deleted. Instead, use exact paths with a single /, which is the child axis. insert node doc("xml.xml")/a/@att into doc("xml.xml")/a/b, delete node doc("xml.xml")/a/@att Thanks. -jb On Tue, Oct 6, 2015 at 12:23 PM, Leo Studer wrote: > Hello > > I am using Oxygen 17.0 with Saxon EE 9.6.0.5 as the xQuery Update > processor. > > I want to move an attribute one level deeper. > > In the example I want to move att="att? from to > > > > > > > Here my code: > > *delete* *node* *doc*("xml.xml")//*@att*, > *insert* *node* *doc*("xml.xml")//*@att* *into **doc*("xml.xml")//*b* > > Each of these two statements work correctly alone but when I try both > together I get java.lang.NullPointerException. > > Can anyone explain what happens here? > > Thanks in advance > Leo > > > > > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at saxonica.com Tue Oct 6 09:56:30 2015 From: mike at saxonica.com (Michael Kay) Date: Tue, 6 Oct 2015 17:56:30 +0100 Subject: [xquery-talk] Update bug? In-Reply-To: References: Message-ID: <54D0F8F4-DB85-4EE8-AD72-560CDE43196B@saxonica.com> Yes, a NullPointerException is prima facie evidence of a bug. Please track progress on it here: https://saxonica.plan.io/issues/2465 Michael Kay Saxonica > On 6 Oct 2015, at 17:23, Leo Studer wrote: > > Hello > > I am using Oxygen 17.0 with Saxon EE 9.6.0.5 as the xQuery Update processor. > > I want to move an attribute one level deeper. > > In the example I want to move att="att? from to > > > > > > > Here my code: > > delete node doc("xml.xml")//@att, > insert node doc("xml.xml")//@att into doc("xml.xml")//b > > Each of these two statements work correctly alone but when I try both together I get java.lang.NullPointerException. > > Can anyone explain what happens here? > > Thanks in advance > Leo > > > > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From g at 28.io Wed Oct 7 01:13:41 2015 From: g at 28.io (Ghislain Fourny) Date: Wed, 7 Oct 2015 10:13:41 +0200 Subject: [xquery-talk] Update bug? In-Reply-To: References: Message-ID: Hi Leo, Joseph, Actually, the semantics of the XQuery Update Facility is based on snapshots, which means that the order of the expressions is irrelevant in terms of updates. Each expression is evaluated against the original document, gathering a set of updates known as a PUL, and the updates are only applied at the very end. Even with the delete coming first, the insert still should see the to-be-deleted node. Even if you swap the two expressions, the engine may still evaluate the second expression first under the hood, or even in parallel, and you won't see any difference. Commas have a monoid (concatenation) semantics when used with items, but no elapse-of-time semantics. The XQuery Update Facility , like XQuery was very cleanly designed as a declarative language :-) I hope it's useful. Kind regards, Ghislain On Tue, Oct 6, 2015 at 6:54 PM, Joseph Bryan wrote: > Hi Leo, > > Try reversing the order of your statements, first inserting the node as a > child of before deleting it. > > Also, you probably don't want to be using // in your selectors, which > means the descendant-or-self axis. With that XPath expression, any @att at > any level of the document would be copied and then deleted. Instead, use > exact paths with a single /, which is the child axis. > > insert node doc("xml.xml")/a/@att into doc("xml.xml")/a/b, > delete node doc("xml.xml")/a/@att > > Thanks. > > -jb > > On Tue, Oct 6, 2015 at 12:23 PM, Leo Studer > wrote: > >> Hello >> >> I am using Oxygen 17.0 with Saxon EE 9.6.0.5 as the xQuery Update >> processor. >> >> I want to move an attribute one level deeper. >> >> In the example I want to move att="att? from to >> >> >> >> >> >> >> Here my code: >> >> *delete* *node* *doc*("xml.xml")//*@att*, >> *insert* *node* *doc*("xml.xml")//*@att* *into **doc*("xml.xml")//*b* >> >> Each of these two statements work correctly alone but when I try both >> together I get java.lang.NullPointerException. >> >> Can anyone explain what happens here? >> >> Thanks in advance >> Leo >> >> >> >> >> >> _______________________________________________ >> talk at x-query.com >> http://x-query.com/mailman/listinfo/talk >> > > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dflorescu at me.com Fri Oct 9 10:38:50 2015 From: dflorescu at me.com (daniela florescu) Date: Fri, 09 Oct 2015 10:38:50 -0700 Subject: [xquery-talk] JSON query language Message-ID: Hello everyone, given that the XML/XQuery didn?t help the JSON community, they went ahead and created their own query language ?maison?, aka ?fait-a-la-main?. https://github.com/couchbaselabs/query/blob/master/docs/n1ql-select.md Note 1: This is considered the DISRUPTIVE technology in JSON world. The other ones are actually much worse. Note 2. Remark the last change to the spec, which says " Allow subqueries in FROM clause. Improves composability.? ?. No comments. Dana -------------- next part -------------- An HTML attachment was scrubbed... URL: From bunce.andy at gmail.com Fri Oct 9 15:31:40 2015 From: bunce.andy at gmail.com (Andy Bunce) Date: Fri, 9 Oct 2015 23:31:40 +0100 Subject: [xquery-talk] asterixdb Message-ID: Hi, Not tried it myself but, AsterixDB [1] may be of interest to XQuery users. >The heart of AQL[2] 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. and >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 [3] Regards /Andy [1] https://asterixdb.ics.uci.edu/ [2] https://asterixdb.ics.uci.edu/documentation/aql/manual.html [3] http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf -------------- next part -------------- An HTML attachment was scrubbed... URL: From dflorescu at me.com Sat Oct 10 03:03:35 2015 From: dflorescu at me.com (daniela florescu) Date: Sat, 10 Oct 2015 03:03:35 -0700 Subject: [xquery-talk] asterixdb In-Reply-To: References: Message-ID: Andy, 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..) Depressing. Are users so ignorant and they prefer a vanilla syntax that they know over significant expressive power ? I wonder. Dana > On Oct 9, 2015, at 3:31 PM, Andy Bunce wrote: > > Hi, > > Not tried it myself but, AsterixDB [1] may be of interest to XQuery users. > > >The heart of AQL[2] 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. > > and > > >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 [3] > > Regards > /Andy > > [1] https://asterixdb.ics.uci.edu/ > [2] https://asterixdb.ics.uci.edu/documentation/aql/manual.html > [3] http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From pavel.velikhov at gmail.com Sat Oct 10 04:41:00 2015 From: pavel.velikhov at gmail.com (Pavel Velikhov) Date: Sat, 10 Oct 2015 14:41:00 +0300 Subject: [xquery-talk] asterixdb In-Reply-To: References: Message-ID: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> N1QL seems to have all the features to support a JSONiq front-end. Seems like a simple translation, except for the group-by clause. I guess if people like 4-valued logic, breaking up constructors into group by and select clauses - let them have it :) > On 10 Oct 2015, at 13:03, daniela florescu wrote: > > Andy, > > 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..) > > Depressing. > > Are users so ignorant and they prefer a vanilla syntax that they know over significant expressive power ? > > I wonder. > > Dana > > > > >> On Oct 9, 2015, at 3:31 PM, Andy Bunce > wrote: >> >> Hi, >> >> Not tried it myself but, AsterixDB [1] may be of interest to XQuery users. >> >> >The heart of AQL[2] 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. >> >> and >> >> >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 [3] >> >> Regards >> /Andy >> >> [1] https://asterixdb.ics.uci.edu/ >> [2] https://asterixdb.ics.uci.edu/documentation/aql/manual.html >> [3] http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf >> >> _______________________________________________ >> talk at x-query.com >> http://x-query.com/mailman/listinfo/talk > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk ? ?????????, ????? ??????? pavel.velikhov at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dflorescu at me.com Sat Oct 10 04:48:38 2015 From: dflorescu at me.com (daniela florescu) Date: Sat, 10 Oct 2015 04:48:38 -0700 Subject: [xquery-talk] asterixdb In-Reply-To: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> References: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> Message-ID: No, Pavel, by no means, NO. While N1Ql is finally something relatively well defined, and MUCH better then the alternatives, in terms of expressive power, we go back to 1993. N1QL is 99% a copy of OQL designed by Sophie Cluet in 1993 for object-oriented databases, which had nested objects and arrays, and After you got used to program in XQuery, going back to N1QL is going back to the cave age. I personally won?t, and I would rather go did cow?s dung (time to review the classics https://www.youtube.com/watch?v=b2F-DItXtZs :-) Here are a couple of things (random things that come to my mind in 3 seconds?..): 1. Compositionality. It?s 2015 , not 1977, for God?s sake. 2. Casts, explicit and implicit casts. Absolutely necessary for processing data of unknown structure. 3. If-then-elses. Absolutely necessary for processing data of unknown structure. 4. try-catch. Absolutely necessary for processing data of unknown structure. 5. Object and array constructors with dynamically computed content. It's 2015, not 1977 for God?s sake. 5. Functions and especially recursive functions. Absolutely necessary for processing data of unknown structure. 6. Declarative updates. No comment. 7. Full text. Again, it 2015, not 1977 for God?s sake. ========= N1Ql is a cute little thing that brings us back in 1993?..:( depressed. Go back digging cow?s dung (or fashion in my case..) while people are still so ignorant in terms of data processing ?? Wake me up when it?s done. Dana > On Oct 10, 2015, at 4:41 AM, Pavel Velikhov wrote: > > N1QL seems to have all the features to support a JSONiq front-end. Seems like a simple translation, except for the group-by clause. > I guess if people like 4-valued logic, breaking up constructors into group by and select clauses - let them have it :) > >> On 10 Oct 2015, at 13:03, daniela florescu > wrote: >> >> Andy, >> >> 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..) >> >> Depressing. >> >> Are users so ignorant and they prefer a vanilla syntax that they know over significant expressive power ? >> >> I wonder. >> >> Dana >> >> >> >> >>> On Oct 9, 2015, at 3:31 PM, Andy Bunce > wrote: >>> >>> Hi, >>> >>> Not tried it myself but, AsterixDB [1] may be of interest to XQuery users. >>> >>> >The heart of AQL[2] 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. >>> >>> and >>> >>> >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 [3] >>> >>> Regards >>> /Andy >>> >>> [1] https://asterixdb.ics.uci.edu/ >>> [2] https://asterixdb.ics.uci.edu/documentation/aql/manual.html >>> [3] http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf >>> >>> _______________________________________________ >>> talk at x-query.com >>> http://x-query.com/mailman/listinfo/talk >> _______________________________________________ >> talk at x-query.com >> http://x-query.com/mailman/listinfo/talk > > ? ?????????, > ????? ??????? > pavel.velikhov at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dflorescu at me.com Sat Oct 10 05:12:44 2015 From: dflorescu at me.com (daniela florescu) Date: Sat, 10 Oct 2015 05:12:44 -0700 Subject: [xquery-talk] asterixdb In-Reply-To: References: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> Message-ID: <964626E4-9D44-483E-A27E-A54D47E95C78@me.com> > > depressed. > > Go back digging cow?s dung (or fashion in my case..) while people are still so ignorant in terms of data processing ?? I am GOING?. :-))) Sorry for the misspelling ?. Dana From dflorescu at me.com Sat Oct 10 05:17:38 2015 From: dflorescu at me.com (daniela florescu) Date: Sat, 10 Oct 2015 05:17:38 -0700 Subject: [xquery-talk] asterixdb In-Reply-To: References: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> Message-ID: And how can I forget to add to the list: PATH EXPRESSIONS with good expressive power. Again, we had them in XML since 1996. It?s 2015, Pavel. 20 years later. Best Dana > On Oct 10, 2015, at 4:48 AM, daniela florescu wrote: > > No, Pavel, by no means, NO. > > While N1Ql is finally something relatively well defined, and MUCH better then the alternatives, > in terms of expressive power, we go back to 1993. > > N1QL is 99% a copy of OQL designed by Sophie Cluet in 1993 for object-oriented databases, which had > nested objects and arrays, and > > After you got used to program in XQuery, going back to N1QL is going back to the cave age. > > I personally won?t, and I would rather go did cow?s dung (time to review the classics https://www.youtube.com/watch?v=b2F-DItXtZs :-) > > Here are a couple of things (random things that come to my mind in 3 seconds?..): > > 1. Compositionality. It?s 2015 , not 1977, for God?s sake. > > 2. Casts, explicit and implicit casts. Absolutely necessary for processing data of unknown structure. > > 3. If-then-elses. Absolutely necessary for processing data of unknown structure. > > 4. try-catch. Absolutely necessary for processing data of unknown structure. > > 5. Object and array constructors with dynamically computed content. It's 2015, not 1977 for God?s sake. > > 5. Functions and especially recursive functions. Absolutely necessary for processing data of unknown structure. > > 6. Declarative updates. No comment. > > 7. Full text. Again, it 2015, not 1977 for God?s sake. > > ========= > > N1Ql is a cute little thing that brings us back in 1993?..:( > > > depressed. > > Go back digging cow?s dung (or fashion in my case..) while people are still so ignorant in terms of data processing ?? > > Wake me up when it?s done. > > Dana > > > >> On Oct 10, 2015, at 4:41 AM, Pavel Velikhov > wrote: >> >> N1QL seems to have all the features to support a JSONiq front-end. Seems like a simple translation, except for the group-by clause. >> I guess if people like 4-valued logic, breaking up constructors into group by and select clauses - let them have it :) >> >>> On 10 Oct 2015, at 13:03, daniela florescu > wrote: >>> >>> Andy, >>> >>> 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..) >>> >>> Depressing. >>> >>> Are users so ignorant and they prefer a vanilla syntax that they know over significant expressive power ? >>> >>> I wonder. >>> >>> Dana >>> >>> >>> >>> >>>> On Oct 9, 2015, at 3:31 PM, Andy Bunce > wrote: >>>> >>>> Hi, >>>> >>>> Not tried it myself but, AsterixDB [1] may be of interest to XQuery users. >>>> >>>> >The heart of AQL[2] 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. >>>> >>>> and >>>> >>>> >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 [3] >>>> >>>> Regards >>>> /Andy >>>> >>>> [1] https://asterixdb.ics.uci.edu/ >>>> [2] https://asterixdb.ics.uci.edu/documentation/aql/manual.html >>>> [3] http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf >>>> >>>> _______________________________________________ >>>> talk at x-query.com >>>> http://x-query.com/mailman/listinfo/talk >>> _______________________________________________ >>> talk at x-query.com >>> http://x-query.com/mailman/listinfo/talk >> ? ?????????, >> ????? ??????? >> pavel.velikhov at gmail.com > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From pavel.velikhov at gmail.com Sat Oct 10 06:46:27 2015 From: pavel.velikhov at gmail.com (Pavel Velikhov) Date: Sat, 10 Oct 2015 16:46:27 +0300 Subject: [xquery-talk] asterixdb In-Reply-To: References: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> Message-ID: Yeah, I kind of missed that? So there will be a N1QL v.2? :) Btw I like OQL much more than N1QL. > On 10 Oct 2015, at 15:17, daniela florescu wrote: > > And how can I forget to add to the list: > > PATH EXPRESSIONS with good expressive power. > > Again, we had them in XML since 1996. > > It?s 2015, Pavel. > > 20 years later. > > > Best > Dana > > > >> On Oct 10, 2015, at 4:48 AM, daniela florescu > wrote: >> >> No, Pavel, by no means, NO. >> >> While N1Ql is finally something relatively well defined, and MUCH better then the alternatives, >> in terms of expressive power, we go back to 1993. >> >> N1QL is 99% a copy of OQL designed by Sophie Cluet in 1993 for object-oriented databases, which had >> nested objects and arrays, and >> >> After you got used to program in XQuery, going back to N1QL is going back to the cave age. >> >> I personally won?t, and I would rather go did cow?s dung (time to review the classics https://www.youtube.com/watch?v=b2F-DItXtZs :-) >> >> Here are a couple of things (random things that come to my mind in 3 seconds?..): >> >> 1. Compositionality. It?s 2015 , not 1977, for God?s sake. >> >> 2. Casts, explicit and implicit casts. Absolutely necessary for processing data of unknown structure. >> >> 3. If-then-elses. Absolutely necessary for processing data of unknown structure. >> >> 4. try-catch. Absolutely necessary for processing data of unknown structure. >> >> 5. Object and array constructors with dynamically computed content. It's 2015, not 1977 for God?s sake. >> >> 5. Functions and especially recursive functions. Absolutely necessary for processing data of unknown structure. >> >> 6. Declarative updates. No comment. >> >> 7. Full text. Again, it 2015, not 1977 for God?s sake. >> >> ========= >> >> N1Ql is a cute little thing that brings us back in 1993?..:( >> >> >> depressed. >> >> Go back digging cow?s dung (or fashion in my case..) while people are still so ignorant in terms of data processing ?? >> >> Wake me up when it?s done. >> >> Dana >> >> >> >>> On Oct 10, 2015, at 4:41 AM, Pavel Velikhov > wrote: >>> >>> N1QL seems to have all the features to support a JSONiq front-end. Seems like a simple translation, except for the group-by clause. >>> I guess if people like 4-valued logic, breaking up constructors into group by and select clauses - let them have it :) >>> >>>> On 10 Oct 2015, at 13:03, daniela florescu > wrote: >>>> >>>> Andy, >>>> >>>> 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..) >>>> >>>> Depressing. >>>> >>>> Are users so ignorant and they prefer a vanilla syntax that they know over significant expressive power ? >>>> >>>> I wonder. >>>> >>>> Dana >>>> >>>> >>>> >>>> >>>>> On Oct 9, 2015, at 3:31 PM, Andy Bunce > wrote: >>>>> >>>>> Hi, >>>>> >>>>> Not tried it myself but, AsterixDB [1] may be of interest to XQuery users. >>>>> >>>>> >The heart of AQL[2] 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. >>>>> >>>>> and >>>>> >>>>> >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 [3] >>>>> >>>>> Regards >>>>> /Andy >>>>> >>>>> [1] https://asterixdb.ics.uci.edu/ >>>>> [2] https://asterixdb.ics.uci.edu/documentation/aql/manual.html >>>>> [3] http://www.vldb.org/pvldb/vol7/p1905-alsubaiee.pdf >>>>> >>>>> _______________________________________________ >>>>> talk at x-query.com >>>>> http://x-query.com/mailman/listinfo/talk >>>> _______________________________________________ >>>> talk at x-query.com >>>> http://x-query.com/mailman/listinfo/talk >>> ? ?????????, >>> ????? ??????? >>> pavel.velikhov at gmail.com >> >> _______________________________________________ >> talk at x-query.com >> http://x-query.com/mailman/listinfo/talk > ? ?????????, ????? ??????? pavel.velikhov at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From g at 28.io Mon Oct 12 04:19:43 2015 From: g at 28.io (Ghislain Fourny) Date: Mon, 12 Oct 2015 13:19:43 +0200 Subject: [xquery-talk] asterixdb In-Reply-To: References: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> Message-ID: Hi, I agree with Dana that XQuery has crucial features that address use cases that emerged over the last decade. Both the SQL experience of the last 45 years and the XQuery experience from the last 15 years should be leveraged by whichever language establishes itself on the document store processing market. I think that ignoring the one or the other would imply a high opportunity cost either way. When describing languages, performance is often emphasized, for good reasons. However, productivity and time-to-market are also very important. I can see every single day how much time and money can be saved using XQuery (or languages derived therefrom) and I would be quite reluctant to switch to a language that doesn't have its features. My 2 cents. Kind regards, Ghislain -------------- next part -------------- An HTML attachment was scrubbed... URL: From dflorescu at me.com Mon Oct 12 14:18:52 2015 From: dflorescu at me.com (daniela florescu) Date: Mon, 12 Oct 2015 14:18:52 -0700 Subject: [xquery-talk] asterixdb In-Reply-To: References: <6C957CD1-2657-42C3-A9B8-F97CB1178AED@gmail.com> Message-ID: <1B667ACC-C9B0-4FA9-8E61-E7D4BCC2B512@me.com> > On Oct 10, 2015, at 6:46 AM, Pavel Velikhov wrote: > > Yeah, I kind of missed that? So there will be a N1QL v.2? :) Huh. I hope not. One cannot add ?support for semi-structuredness? to a query language as an AFTER TOUGHT. If you do that, you end up with new version of SQL-XML, which is a query language that only a tender mother can love. Best Dana -------------- next part -------------- An HTML attachment was scrubbed... URL: From geert.josten at gmail.com Wed Oct 14 03:01:37 2015 From: geert.josten at gmail.com (Geert Josten) Date: Wed, 14 Oct 2015 12:01:37 +0200 Subject: [xquery-talk] [ANN] XML Amsterdam 2015 Early Bird discount Message-ID: You can still get Early Bird discount for XML Amsterdam 2015. Get discount for you, as well as colleagues! http://xmlamsterdam.com/2015/registration Keynotes by Norm Walsh, and Steven Pemberton. Speaking this year Alain Couthures, Eric van der Vlist, Gerrit Imsieke, and a large number of others. http://xmlamsterdam.com/2015/program We also have a Pre-conference this year. It includes an XForms Day organized by Steven Pemberton, and there are a few rooms left for other initiatives. http://xmlamsterdam/2015/pre-conference Special thanks to CWI, and W3C for providing a venue. http://xmlamsterdam.com/2015/venue Feel free to contact us with any question or idea regarding the conference at info at xmlamsterdam.com! http://xmlamsterdam.com/ http://twitter.com/xmlamsterdam -------------- next part -------------- An HTML attachment was scrubbed... URL: From dflorescu at me.com Sat Oct 31 13:05:16 2015 From: dflorescu at me.com (daniela florescu) Date: Sat, 31 Oct 2015 14:05:16 -0700 Subject: [xquery-talk] specification for Microsoft's U-SQL ? Message-ID: <93679119-E2DC-49E8-95E4-5789B959E15E@me.com> Seems interesting in principle. http://thenewstack.io/meet-u-sql-microsofts-new-language-big-data/ But anyone in a luck to see a specification for it ? Thanks for any pointer, best regards Dana