Phil Rzewski

@zmajeed: Thanks for the pointer to JavaScript's `Regexp.exec()`. Indeed, we may use that for inspiration. Regarding the nested fields, in case you bump into this elsewhere, note that there's a...

@zmajeed: Thanks for reporting your `nest_dotted(groups)` not seeming to have any effect. It turns out that's a new bug, so a fix for that is being tracked via #4914. Someone's...

Update: The initial `grok()` support has been merged (#4827) but it doesn't yet support their own named capture support (such as is shown in the [first syntax for custom patterns](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_custom_patterns)...

Thanks for pointing out the Postgres behavior @mattnibs. Yeah, this one was earlier in my work with sqllogictest before I was in the habit of only filing issues when I...

@nwt took a look at this and reported that the perf delta is due to some new "yields" that occur in the revised approach. This is something we could improve...

@chrismo: Yes, I understand this can be confusing. I've bumped up against this as a user, myself. You were on the right track with your hunch about `parse_zson()`, but below...

@chrismo: Correct. When they're coming in via `echo` those values you're showing are treated as human-readable Super (SUP) (which has been called "Super JSON (JSUP)" recently, but is in the...

@chrismo: I'm pleased to report this one has been addressed. To summarize, [the comment above](https://github.com/brimdata/super/issues/5747#issuecomment-2777329345) mentioned that to fix this would likely require "change to how type decorators look in...

In reviewing this issue, @nwt correctly pointed out that the systems that have been around longer offer knobs that could effectively have them do the same null treatment we showed...

Fair enough. When the queries are different it's not always obvious to me when they share a root cause.