Maximilian Roos

(I haven't got to this but this is a great issue and very helpful for showing the current gaps @richb-hanover , so thank you. Some of this is in the...

> Instead, we should provide better language features to steer people away from the thing you wanted to do here. Very much agree! > We may need some type of...

Thanks for the issue @GavinRay97 . I agree Lateral joins are very useful! They're not supported on every dialect, but that doesn't mean we can't add them. We approach new...

The FAQ is quite the aesthetic rollercoaster:

That is better much for the inline code snippets. I'm no UI designer but maybe the inline could be in light mode; maybe there's too much difference when doing dark...

Now with #908 — a stopgap while we redo some of the Semantic part of the compiler — this now compiles to: ```sql WITH x AS ( SELECT x_id, common_fieldname...

Thanks for the issue @ajfriend . We touched on this here: https://github.com/prql/prql/issues/469. I'm open-minded; I tend to agree that a list is quite a logical conclusion from a list that...

Yes that would be great. (FWIW DuckDB can do the latter, but I think that's the only one)

I think that's good! Does this compile to the same SQL for most dialects?

Great. We'd need to work out a way of distinguishing based on the type of the arg from the stdlib, which isn't yet supported, but could be supported by #593....