-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Ability to prevent dropping an index when a column referencing the index is dropped #73445
Copy link
Copy link
Open
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-communityOriginated from the communityOriginated from the communityT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Description
Is your feature request related to a problem? Please describe.
Currently, dropping a column that is referenced by an index (either directly or via STORING) will silently drop the index as well. Although this is described in the CockroachDB documentation, it is considered dangerous by a customer who runs a large on-prem microservice environment where they operate DBaaS for internal customers.
Describe the solution you'd like
Provide the ability not to drop the index on an opt-in basis (either via a cluster/session setting or CASCADE)
Describe alternatives you've considered
N/A
Jira issue: CRDB-11592
Epic CRDB-60817
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-communityOriginated from the communityOriginated from the communityT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)