You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What feature or improvement would you like to see?
Although most Adbc methods throws AdbcException, there are several places in ADBC interfaces where methods throws Exception (notably for close() methods) or IOException. Similar to JDBC API, all exceptions should be normalized around AdbcException to make API consistent.
It would be an incompatible API change though. When updating methods from Exception to AdbcException, this would be a source incompatible change but a binary compatible one. However when changing from IOException to AdbcException, it would be a source and binary incompatible change.
The text was updated successfully, but these errors were encountered:
ADBC base classes/interfaces are not consistent in using `AdbcException`
for all their methods (sometimes `Exception` or `IOException` are used).
Introduces `AdbcCloseable` which is a subinterface of `AutoCloseable`
throwing `AdbcException` instead of `Exception` and replace usage of
`AutoCloseable` in core interfaces with `AdbcCloseable`
Also replaces use of `IOException` in `QueryResult` with
`AdbcException`.
Fixesapache#2237
What feature or improvement would you like to see?
Although most Adbc methods throws
AdbcException
, there are several places in ADBC interfaces where methods throwsException
(notably forclose()
methods) orIOException
. Similar to JDBC API, all exceptions should be normalized aroundAdbcException
to make API consistent.It would be an incompatible API change though. When updating methods from
Exception
toAdbcException
, this would be a source incompatible change but a binary compatible one. However when changing fromIOException
toAdbcException
, it would be a source and binary incompatible change.The text was updated successfully, but these errors were encountered: