zlacker

>>legran+(OP)
reminds me PRQL https://prql-lang.org

and SPL from Splunk

>>slt202+L5
Reminds me of KQL (Kusto Query Language) by Microsoft

>>mark_a+q8
Yeh, when I saw the example above I thought it was KQL.

But they do sort of acknowledge it in the paper. Eg on the first page it says:

> …we present a solution – adding pipe-structured data flow syntax to SQL. This makes SQL more flexible, extensible and easy to use. This paradigm works well in other languages like Kusto’s KQL[5]

Strange typo though, to say “Kusto’s KQL” instead of “Microsoft’s KQL”

Kusto is allegedly named after (sort of in reference to) Jacques Cousteau, so “Kusto’s” doesn’t make sense.

>>LeonB+Bm
unfortunately KQL doesn't seem to have INSERT, UPDATE etc. support, it seems to be a pure query language for querying. Unless this strange different .insert syntax is what they intended for their language from the start? I don't know: https://learn.microsoft.com/en-us/kusto/management/data-inge...

>>Nathan+Bs
> unfortunately KQL doesn't seem to have INSERT, UPDATE etc.

(Disclaimer: I'm an engineer at Microsoft, and I use Kusto basically every day)

This seems to me to be a deliberate design choice. Microsoft doesn't want engineers mutating the databases by hand. There are mechanisms to do that (mostly outside of Kusto, and usually to resolve privacy incidents), but the common case of querying is not supposed to allow for arbitrary changes to the database.