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
Previously, we did not track dependencies on target columns in the SET clause
of an UPDATE statement while creating a routine. This meant that it was
possible to break a routine by dropping such a column if it wasn't referenced
elsewhere in the routine. This commit fixes the bug by adding target columns
that are explicitly referenced by an UPDATE statement to the routine
dependencies. The new behavior is gated behind the session variable
`prevent_update_set_column_drop`.
Fixes#158898
Release note (bug fix): Fixed a bug that allowed a column to be dropped from
its table despite being referenced by a routine. The bug could happen when the
column was only referenced as a target column in the SET clause of an UPDATE
statement within the routine. This fix only applies to newly-created routines.
In versions prior to v26.1, the fix must be enabled by setting the session
variable `prevent_update_set_column_drop`.
0 commit comments