sql/schemachanger: implement CREATE OR REPLACE TRIGGER#162633
Merged
trunk-io[bot] merged 1 commit intocockroachdb:masterfrom Feb 13, 2026
Merged
sql/schemachanger: implement CREATE OR REPLACE TRIGGER#162633trunk-io[bot] merged 1 commit intocockroachdb:masterfrom
trunk-io[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
Contributor
|
😎 Merged successfully - details. |
Member
|
This change is |
rafiss
force-pushed
the
trigger-replace
branch
from
944a186 to
4d05c30
Compare
Previously, CREATE OR REPLACE TRIGGER returned an unimplemented error. This commit implements the feature by resolving any existing trigger with the same name on the table and dropping it before creating the replacement trigger with a new trigger ID. The approach follows the same pattern as DropTrigger: only the Trigger and TriggerDeps elements are explicitly dropped, and the dependent elements (TriggerName, TriggerEnabled, TriggerTiming, etc.) are cleaned up by the existing dependency rules. A new trigger ID is allocated for the replacement because the declarative schema changer does not allow re-adding an element with the same key as one dropped in the same transaction. The intermediate drop is safe because triggers cannot have dependents (nothing depends on a trigger), so there is no cascade concern. Fixes: cockroachdb#128422 Epic: CRDB-42942 Release note (sql change): CREATE OR REPLACE TRIGGER is now supported. If a trigger with the same name already exists on the same table, it is replaced with the new definition. If no trigger with that name exists, a new trigger is created.
rafiss
force-pushed
the
trigger-replace
branch
from
4d05c30 to
f7ab06e
Compare
fqazi
approved these changes
Feb 13, 2026
Collaborator
fqazi
left a comment
fqazi
left a comment
There was a problem hiding this comment.
@fqazi reviewed 4 files and all commit messages, and made 1 comment.
Reviewable status:complete! 1 of 0 LGTMs obtained (waiting on @rafiss).
Collaborator
Author
|
/trunk merge tftr! |
celeste-cockroachdb
Bot
added
v26.2.0-prerelease
and removed
target-release-26.2.0
labels
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, CREATE OR REPLACE TRIGGER returned an unimplemented error. This commit implements the feature by resolving any existing trigger with the same name on the table and dropping it before creating the replacement trigger with a new trigger ID.
The approach follows the same pattern as DropTrigger: only the Trigger and TriggerDeps elements are explicitly dropped, and the dependent elements (TriggerName, TriggerEnabled, TriggerTiming, etc.) are cleaned up by the existing dependency rules. A new trigger ID is allocated for the replacement because the declarative schema changer does not allow re-adding an element with the same key as one dropped in the same transaction.
The intermediate drop is safe because triggers cannot have dependents (nothing depends on a trigger), so there is no cascade concern.
Fixes: #128422
Release note (sql change): CREATE OR REPLACE TRIGGER is now supported. If a trigger with the same name already exists on the same table, it is replaced with the new definition. If no trigger with that name exists, a new trigger is created.