We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
Currently i wrap Vec<u32> as MyVec and implement something like this:
Vec<u32>
MyVec
impl duckdb::ToSql for MyVec<u32> { #[inline] fn to_sql(&self) -> duckdb::Result<duckdb::types::ToSqlOutput<'_>> { Ok(duckdb::types::ToSqlOutput::from(format!("{:?}", self.0))) } }
I think however that such crude string formatting is highly inefficient. There is support for UInt(u32) (https://duckdb.org/docs/sql/data_types/overview.html, https://docs.rs/duckdb/latest/duckdb/types/enum.Value.html#variant.UInt) however I'm not sure why there is only Blob(u8) (https://docs.rs/duckdb/latest/duckdb/types/enum.Value.html#variant.Blob). DuckDB says ARRAY supports arbitrary types underneath (https://duckdb.org/docs/sql/data_types/array).
UInt(u32)
Blob(u8)
ARRAY
Or should I use List instead (https://docs.rs/duckdb/latest/duckdb/types/enum.Value.html#variant.List) ?
List
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
Currently i wrap
Vec<u32>
asMyVec
and implement something like this:I think however that such crude string formatting is highly inefficient. There is support for
UInt(u32)
(https://duckdb.org/docs/sql/data_types/overview.html, https://docs.rs/duckdb/latest/duckdb/types/enum.Value.html#variant.UInt) however I'm not sure why there is onlyBlob(u8)
(https://docs.rs/duckdb/latest/duckdb/types/enum.Value.html#variant.Blob). DuckDB saysARRAY
supports arbitrary types underneath (https://duckdb.org/docs/sql/data_types/array).Or should I use
List
instead (https://docs.rs/duckdb/latest/duckdb/types/enum.Value.html#variant.List) ?The text was updated successfully, but these errors were encountered: