Phil Rzewski

I revisited this issue in the SuperSQL era. If we attempt a similar join in Postgres it fails there as well, though it happens to deliver a helpful error message...

Here is verification as of super commit cc6b1e6 of the initial subquery support added in #6070. Revisiting the simple repro query shown above, we now see: ``` $ super -version...

To mark our continued progress toward comprehensive subquery support, here's an example showing the first pass of correlated subquery support in pipe syntax added in #6100 to deliver the equivalent...

Here's verification in Zed commit 3a40788 of the [`map()` function](https://zed.brimdata.io/docs/next/language/functions/map) added in #4806 that handles this for arrays and sets. Revisiting the original example above, instead of the `over` /...

Here's an update as of current super commit 4493acd. In addition to having addressed the bug linked from the last comment above, there's now building blocks for a flexible approach...

@zmajeed: RE: "move operator". I think this turns out to be another language design topic. Similar to how `mv` in UNIX/Linux can be used to rename files in the same...

@nwt pointed out that a good way to resolve the clash would be to have our string interpolation behave more like [Python's f-strings](https://peps.python.org/pep-0498/).

Verified in Zed commit e40a039. Now that string interpolation uses F-strings and hence there's no longer a clash, the examples above that use `${}` now work as expected. ``` $...

Also, I'd mentioned when I opened this issue that it'd be worth adding an example to the `regexp_replace()` docs that uses curly braces. Now that this issue has been fixed,...

A user found themselves asking about this functionality in a recent [community Slack thread](https://brimdata.slack.com/archives/CTSMAK6G7/p1723838165239319?thread_ts=1723833517.874349&cid=CTSMAK6G7). In their own words: >i guess this probably couldn’t easily be dealt with … using NONNEGINT...