I'd be very interested if I can help in any way with porting ADBC to more languages, and learning more about use cases/what functionality is useful (e.g. are you looking to have a full driver/client ecosystem in C♯, or are you interested in being able to leverage drivers written in C/C++/Go?)
>From a quick look, C♯ follows C++, Python, etc. in putting child fields as >part of the nested type, rather than as part of the field itself. I can't say >why precisely one implementation chose one design or another, but Java >basically follows the IPC format exactly in this regard (and others, e.g. it >has a parameterized Int type rather than Int32, Int64, UInt32, etc.), while >the other languages model it at a higher level (because only some types can >have children). What specifically is difficult with the how the APIs are structured? On Thu, Mar 9, 2023, at 15:19, David Coe wrote: > I am interested in the difference between how a Field is structured in > Java (with children) and in C# (no children) and why that's the case. > > I am looking to port apache/arrow-adbc: Apache arrow > (github.com)<https://github.com/apache/arrow-adbc> to C# but the > concept of children is making it a little hairy. > > > * David
