dlurton

29 ms·

1. 1.▲
   by dlurton 7y ago

   Also, the PartiQL compiler makes heavy use of closures, each of which becomes a class, so the first time a query executes the JVM has to load a few dozen classes--this probably explains the 86ms more than a lack of JIT optimizations alone.
2. 2.▲
   by dlurton 7y ago

   ORDER BY is still in the works: https://github.com/partiql/partiql-lang-kotlin/issues/47
3. 3.▲
   by dlurton 7y ago

   One big difference is native support for nested data that's built right into the syntax of the language. Most other SQL implementations allow support for nested data through functions which have non-intuitive syntax.
4. 4.▲
   by dlurton 7y ago

   It would be possible to integrate parquet data with PartiQL. Here is an example of integrating PartiQL with CSV files. https://github.com/partiql/partiql-lang-kotlin/blob/master/e... . Integrating with
5. 5.▲
   by dlurton 7y ago

   This is on the JVM so the JIT's optimizations probably haven't kicked in yet.