Gábor E. Gévay
Gábor E. Gévay
That would be great, thx!
> could you give me an example of a function that may introduces nulls or a function that does not? The current implementations of `BinaryFunc::introduces_nulls` and `VariadicFunc::introduces_nulls` list some functions...
Maybe a simpler way to explain "introduces null" is to say that "it might make a null result from non-null inputs".
Merged https://github.com/MaterializeInc/materialize/pull/14441, after which this query doesn't cause a panic anymore, but instead prints a proper error msg to the user about hitting the recursion limit. A proper fix that...
OK, I resolved the `this` issue by mostly copy-pasting the solution that you linked above.
Yes, we can certainly compare code complexity, and maybe also performance.
> it's just not so easy to add it at the moment as we need to integrate some notion of keys and identity in order to make the transformation safe...
So if I add the following code at the end of `SourceLangSpec` ``` "aaaa" - { "bbbb" in { val t = reify { val x = 7 x }...
The first example is accessing a `stateful` with a `.bag()` call from inside the UDF of an `updateWith*` call on it. It is not clear whether the user - wants...
Also mentioned in https://github.com/MaterializeInc/materialize/issues/7409