paul-rogers commented on PR #12709: URL: https://github.com/apache/druid/pull/12709#issuecomment-1203315440
Release note item: In previous releases, Druid would automatically close the JDBC `Statement` when the `ResultSet` is closed. Druid would close the `ResultSet` on EOF. Druid would close the statement on any exception. This behavior is, however, non-standard. In this release, Druid's JDBC driver follows the JDBC standards more closely: * The `ResultSet` closes automatically on EOF, but does not close the `Statement` or `PreparedStatement`. Your code must close these statements, perhaps by using a try-with-resources block. * The `PreparedStatement` can now be used multiple times with different parameters. (Previously this was not true since closing the `ResultSet` closed the `PreparedStatement`.) * If any call to a `Statement` or `PreparedStatement` raises an error, the client code must still explicitly close the statement. According to the JDBC standards, statements are not closed automatically on errors. This allows you to obtain information about a failed statement before closing it. If you have code that depended on the old behavior, you may have to change your code to add the required close statement. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
