In other words, do they support storing text/blob that has length larger than 2^32 (4GiB)?
If yes, then the type of TEXT should always be LargeUtf8 (and Uft8 is coerced into LargeUft8).
If no, then the type of TEXT should always be Utf8 (and coercion is reversed).
Similar for binary types.
DuckDB kindly answers this question by returning a schema that contain Utf8 when you declare a column as VARCHAR or TEXT.
This means that it might not be possible to store an Arrow in a database. We need an error for that. And we need to indicate that in coerce_type.
In other words, do they support storing text/blob that has length larger than 2^32 (4GiB)?
If yes, then the type of
TEXTshould always beLargeUtf8(andUft8is coerced intoLargeUft8). If no, then the type ofTEXTshould always beUtf8(and coercion is reversed). Similar for binary types.DuckDB kindly answers this question by returning a schema that contain
Utf8when you declare a column asVARCHARorTEXT.This means that it might not be possible to store an Arrow in a database. We need an error for that. And we need to indicate that in
coerce_type.