[LeonB]

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.

[Nathanba]

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...

[trobertson]

> 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.

[LeonB]

Good question, I don’t know i’ve only used it for querying.

For SQL to Have a good/improved syntax for insert/update/delete/merge would be very nice (in theory)

[_huayra_]

Does KQL still enforce no blank lines in the `let` clauses to the expression?

When I last used KQL, it was infuriating that I could create my `let` clauses in chunks separated by whitespace because a blank line would be considered a terminated statement (and Kusto would say "Hey where's your expression?!"). This meant every Kusto file was a sea of text with no clear differentiation between subsequent clauses. I ended up using 3 blank comment lines as a "fake empty line" just to maintain my sanity.

Again, hope they fixed that by now...

[LeonB]

I’m not sure if that’s fixed, it seems pretty much “by design”, with the way the editor (in the browser) selects the “current query” for you.

[beoberha]

I’m nearly positive that’s an editor “feature”. If you submit queries via the API, you can have blank lines.