sdebruyn commented on issue #588: URL: https://github.com/apache/arrow-adbc/issues/588#issuecomment-2852165398
>But this underscores the point that not all C# code is compatible with AOT compilation. The Google code we're using in the C# BigQuery implementation, for instance, uses Reflection in a way that is not. Now I'd vaguely expect the latest C# SqlClient implementation to be AOT-compatible due to its relative importance in the ecosystem -- but pretty much the only way to determine this conclusive is to try it. So maybe the [go driver](https://github.com/microsoft/go-mssqldb) is a better place to start from, since it will always be able to produce AOT compiled binaries? >From a perhaps overly-selfish perspective, the only personal benefit I would see from an MSSQL ADBC driver is if it offered better performance than using SqlClient via its ADO.NET API. There are tools which exclusively support ADBC drivers. So even to have it available for compatibility reasons could be good enough. >And if the underlying driver happened to support AOT compilation, then so would the combination of the driver and the wrapper. That's a lot of ifs :) Is the reason why you'd not consider the go driver pure personal preference? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
