Thijs

I was playing around with it and happened to stumble upon a bug: ```patch diff --git a/extension/inet/include/html_charref.hpp b/extension/inet/include/html_charref.hpp index d86712db3f..cff46660ec 100644 --- a/extension/inet/include/html_charref.hpp +++ b/extension/inet/include/html_charref.hpp @@ -2493,7 +2493,7 @@ private:...

How do we deal with entity references that expand to multiple codepoints? ```json "≂̸": { "codepoints": [8770, 824], "characters": "≂̸" }, ``` This seems to be different from python's html.unescape...

I think we should rethink this a bit, @soerenwolfers brings up a good point, there is no good reason to allow replacement scans to find objects outside of the regular...

The original issues this PR intended to fix will be moved to a future PR Some issues around replacement scans need to be addressed first, and perhaps around the connection...

Hmm that is expected behavior, but I see how that could be unexpected after having explicitly called `execute` on the relation. To explain a bit of why this is happening:...

Actually this is perhaps a piece of behavior that is not properly documented elsewhere: ```c++ if (scope == SetScope::GLOBAL) { config.SetOption(name, std::move(target_value)); } else { auto &client_config = ClientConfig::GetConfig(context); client_config.set_variables[name]...

The main reasoning behind this is that the relational API mostly speaks to people that are not fond of SQL, so using the relational version wherever we can will speak...

I'm not entirely sure yet how to weave the new expression API into these docs though It might just need a separate page and then we can extend the Transformations...

Thanks! Feel free to make a PR extending our native python expression API as well when necessary. Taking as an example shows how easy these additions can be :)

Please merge with main and address the colesce todo, the linked PR has been merged Thanks for your efforts to extend the support of the spark API!