From 682d6f9d8ab6657f4748192098192d4d230098fe Mon Sep 17 00:00:00 2001 From: Metabase Automation User Date: Sat, 5 Sep 2026 02:13:51 +0000 Subject: [PATCH] Update docs for v63,62 --- _docs/latest/developers-guide/driver-changelog.md | 6 ++++++ _docs/v0.63/developers-guide/driver-changelog.md | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/_docs/latest/developers-guide/driver-changelog.md b/_docs/latest/developers-guide/driver-changelog.md index f24418c45e..290866ba49 100644 --- a/_docs/latest/developers-guide/driver-changelog.md +++ b/_docs/latest/developers-guide/driver-changelog.md @@ -15,6 +15,12 @@ latest: true ## Metabase 0.63.0 +- `metabase.driver.sql-jdbc.execute/cancelation-poisons-connection?` `[driver]` -- whether canceling a `Statement` + leaves the `Connection` unfit for the next query, so that it must be discarded rather than returned to the + connection pool. The query processor cancels a `Statement` whenever reduction stops before the `ResultSet` runs out + of rows, which abandons a result set the server is still producing. Defaults to `false`, because most drivers + recover on their own; `:sqlserver` overrides it to `true`. + - `metabase.driver/validate-impersonated-query` `[driver query]` now has a `:sql-jdbc` implementation that enforces, for every JDBC driver, that a connection-impersonated native query is a single statement. diff --git a/_docs/v0.63/developers-guide/driver-changelog.md b/_docs/v0.63/developers-guide/driver-changelog.md index 0654b0bbc3..42d7278c63 100644 --- a/_docs/v0.63/developers-guide/driver-changelog.md +++ b/_docs/v0.63/developers-guide/driver-changelog.md @@ -13,6 +13,12 @@ layout: new-docs ## Metabase 0.63.0 +- `metabase.driver.sql-jdbc.execute/cancelation-poisons-connection?` `[driver]` -- whether canceling a `Statement` + leaves the `Connection` unfit for the next query, so that it must be discarded rather than returned to the + connection pool. The query processor cancels a `Statement` whenever reduction stops before the `ResultSet` runs out + of rows, which abandons a result set the server is still producing. Defaults to `false`, because most drivers + recover on their own; `:sqlserver` overrides it to `true`. + - `metabase.driver/validate-impersonated-query` `[driver query]` now has a `:sql-jdbc` implementation that enforces, for every JDBC driver, that a connection-impersonated native query is a single statement.