> If your audience is "regular developers" then they often do not know or want
> to speak Arrow.
That's a good point. The thing is that I don't really have an audience
- it is just something I
needed and have now open sourced it if anyone finds it useful too. It
really goes against what
"regular
I'm not sure I understand what you mean with "a wrapper of standards
like ADBC and ODBC".
Do you mean it would use ADBC/ODBC for implementation of the
connector, but still expose its API as Rust traits?
Or do you mean it would replace its API with ADBC and remain using
Rust implementation of datab
Felipe's points are good.
I don't know that you need to adapt the entire ADBC, it sort of depends
what you're after. I see what you've got right now as more of an SQL
abstraction layer. For example, similar to things like [1][2][3] (though 3
is more of an ORM). If you like the SQL interface tha
Two comments:
——
Since this library is analogous to things like ADBC, ODBC, and JDBC, it’s
more of a “driver” than a “connector”. This might make your life easier
when explaining what it does.
It’s not a black and white thing, but “connector” might imply networking to
some people.
I believe you
Hello good folks of Apache Arrow! I come looking for feedback on my
Rust crate connector_arrow [1], which is an Arrow database client that
is able to connect to multiple databases over their native protocols.
It is very similar to ADBC, but better adapted for the Rust ecosystem,
as it can be compi