Re:ArangoDB 2.3: Overhauled query optimizer, AQL improvement...
by schmichael on Thursday November 20, 2014 @01:24PM
(#8637205)
> Because it's a graph database so it doesn't really fit naturally with SQL.
Interesting, but lacking in details. The trivial examples I see in posts like this always seem to map perfectly to SQL.
Re:ArangoDB 2.3: Overhauled query optimizer, AQL improvement...
by fceller on Thursday November 20, 2014 @02:13PM
(#8637476)
I agree, we should show more examples.
AQL was indeed inspired by XQuery. We made some user acceptant tests at the very start and used a version which was using keywords from SQL and a more descriptive approach with keywords from programming languages. At least our test users were mostly confused by a similar SQL-syntax but slightly different SQL sematic.
We talked to the JSONiq guys. They had a look as XQuery and AQL and made a similar decision.
Re:ArangoDB 2.3: Overhauled query optimizer, AQL improvement...
by phpnode on Thursday November 20, 2014 @02:16PM
(#8637496)
https://www.arangodb.com/key-features#aql does a relatively good job explaining it. The examples are all fairly simple, in a real world app you have much more complicated queries and it's here where arango really shines imho. With SQL it's very easy to write inefficient queries by accident, whereas AQL is a lot more explicit.
As far as I can tell from a cursory glance, FOR -> SELECT, IN -> FROM, FILTER -> WHERE, SORT -> ORDER BY.
Is there a reason the authors didn't use the more familiar SQL keywords?