ghislainfourny

5 ms·

1. 1.▲
   by ghislainfourny 2mo ago

   +1 on Johannes SQL was designed for tables and does this job indisputably well. However, even adding dots, lateral joins, and variants, it was not made for nested, heterogeneous data and reaches its limits with many levels of nestedness or
2. 2.▲
   by ghislainfourny 2mo ago

   Congratulations, Johannes!
3. 3.▲
   by ghislainfourny 5y ago

   Thank you for your question. This is, in fact, not an assignment, but a variable binding that is highly optimizable by an execution engine. The let clause is part of the FLWOR expression, works in orchestration with for, where, group by, or
4. 4.▲
   by ghislainfourny 5y ago

   There is also a docker version that should ease the process: https://hub.docker.com/r/rumbledb/rumble
5. 5.▲
   by ghislainfourny 5y ago

   Thank you for your comment. There exist indeed recent extensions of SQL that add support for denormalized data (arrays, objects), for example in Spark SQL and PostgreSQL, however SQL was originally designed for tables and it remains cumbers
6. 6.▲
   by ghislainfourny 5y ago

   Thank you for your comment. The motivation for JSONiq and RumbleDB is discussed in this recent paper, the core argument is data independence: https://arxiv.org/abs/1910.11582v3 JSONiq is a functional language and thus
7. 7.▲
   by ghislainfourny 5y ago

   Thank you for your feedback. The tutorial was moved over to an interactive notebook that you can find here: https://colab.research.google.com/github/RumbleDB/rumble/blo... The easiest way to get started local