CurtHagenlocher commented on issue #4242: URL: https://github.com/apache/arrow-adbc/issues/4242#issuecomment-6178522881
Now that I'm (finally!) finishing ADBC 1.1 support in the .NET implementation, I've been reminded of this gap again and would like to agree on an approach in time for ADBC 1.2. I think there are fundamentally two approaches we could take: 1) Version the `AdbcErrorDetail` structure in some way so that newer drivers can return an additional type specifier. 2) Replace the existing error detail functions with a new function or functions. For the first option, we could in principle use the size to encode both a size and a type by using the high 3 bits to encode the type. I think this can be made to work out correctly, though I also think it's the kind of approach that will invariably lead to a security problem at some point. For the second options, I've proposed using either a schema plus array or an Arrow variant -- but of course other choices are possible. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
