Maximilian Roos

> but now, CSV looks better because it has headers at the top. CSV is not a great format, but it does have this one advantage! Are there nicer formats...

> Also, currently this is a valid query: Ah, I didn't even realize that! That's great! > SQL has that: > > ``` > INSERT INTO employees (first_name, age) VALUES...

Postgres has something decent for this: https://www.postgresql.org/docs/current/queries-values.html

Great! I am some of the way through it, I paused last week, but I can finish it off!

Yes, agree, I think the ``` from `file:/C:/data/employees.csv` ``` could work now; it compiles to: ``` SELECT "file:/C:/data/employees".csv.* FROM "file:/C:/data/employees".csv ``` So possibly we want just `SELECT *` there, but...

This was great, too: https://www.osohq.com/post/building-vs-code-extension-with-rust-wasm-typescript It seems like they took their own approach rather than building on something like https://github.com/ebkalderon/tower-lsp. I'm not sure whether writing something for Monaco / Monarch...

https://github.com/prql/prql/issues/656#issuecomment-1174713630 has some good suggestions. The `UNION` operation is fairly different from most operations in SQL, so it makes sense that it feels a bit foreign. I don't have strong...

Do you think it should be more a function that takes two parameters[^1] — or like a transform like `join` is, connecting the pipeline above? [^1]: or a list

Yes, great point! Technically, we can't then have a list; we'd need exactly two parameters (or to change how we do parameters).

Yeah, I think we can iterate on that along with https://github.com/prql/prql/issues/648 around generalizing over single items & lists. I can imagine some syntheses of these — e.g. the final argument...