b3tt3rw0rs3

4 ms·

1.
by b3tt3rw0rs3 6y ago
Composeability is front and center in GQL, so you may want to consider it.
2.
by b3tt3rw0rs3 7y ago
How would you think anyone should call a graph query language done by the SQL committee?
3.
by b3tt3rw0rs3 7y ago
Many standards are also available via the national standards body of your locale (e.g. ANSI), often at a cheaper rate.
4.
by b3tt3rw0rs3 7y ago
Just say ISO GQL
5.
by b3tt3rw0rs3 7y ago
Just looking at https://db-engines.com/en/ranking/graph+dbms clearly shows Neo4j as the most prominent graph db. I think even Cosmos as number 2 might be misleading here, as Cosmos is a multi-model product and db
6.
by b3tt3rw0rs3 7y ago
AQL is a vendor-specific multi model language that lately has picked up some ideas from openCypher, like pattern matching. GQL is a project for creating an International Standard language in the process of being created by experts from many
7.
by b3tt3rw0rs3 7y ago
SPARQL requires buy-in into the world of the semantic web even when all you want to do is store and query graph data. Also, property graphs wouldn't have managed to get the traction they have if SPARQL would have been sufficient. SPARQ
8.
by b3tt3rw0rs3 7y ago
Standards happen when the time is right. Property graphs have been in the making and matured for the last 10+ years, driven by Neo4j, other vendors, and the community and are going to stay. It's a sign of success that the SQL standards
9.
by b3tt3rw0rs3 7y ago
The GQL project just started. Since it is going to be an ISO standard, the specification is only available for members while under development but may be purchased from ISO once final (Same as for SQL, though you can find copies on the inte