Pedro Holanda

Hey, @NickCrews this issue is similar to #4268. The reason why Arrow dictionaries are not exported to ENUMs is the following: "The Arrow Dictionary is not the same as an...

I think that could be an option, although I'm not exactly sure how to integrate with that. My guess is that the unification will have a considerable extra cost since...

Very true. This could only be added to table objects.

This has been converted to a bunch of different issues.

@Mytherin it seems to me that this issue will affect all our APIs, is there a specific reason to turn query errors into strings? If not we should probably change...

What is the rationale for just having the string (with the addition of an exception type) and not the duckdb::Exception in there?

@Mause I've chatted with Mark about this, the reason to not use Duckdb exceptions is mainly due to their copying being unnecessarily complicated. In this case, maybe we should create...

The appender probably doesn't work because enum is currently not supported on it. The C API should work though, if I try the following code, based on yours, works fine....

Moving this issue to: https://github.com/duckdblabs/substrait/issues/2

Is it a DuckDB problem that PyArrow raises OSEerrors?