-
Notifications
You must be signed in to change notification settings - Fork 3.9k
sql/triggers: add triggers to the random schema workload #146580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
When adding a new declarative schema changer statement, part of our process is to add testing for it to the random schema changer workload. Reach out to the foundations team if any help is needed. |
Moving this back to sql foundations team as the issues being discovered in #142370 seem to indicate a big gap in testing coverage for dependencies in triggers. @Dedej-Bergin: I have assigned it to you for now as part of oncall. Thanks! |
Added coverage for `CREATE TRIGGER` and `DROP TRIGGER` to the Random Schema Changer Workload. Fixes: cockroachdb#146580 Epic: CRDB-42942 Release note: none
Added coverage for `CREATE TRIGGER` and `DROP TRIGGER` to the Random Schema Changer Workload. Fixes: cockroachdb#146580 Epic: CRDB-42942 Release note: none
Added coverage for `CREATE TRIGGER` and `DROP TRIGGER` to the Random Schema Changer Workload. Fixes: cockroachdb#146580 Epic: CRDB-42942 Release note: none
Added coverage for `CREATE TRIGGER` and `DROP TRIGGER` to the Random Schema Changer Workload. Fixes: cockroachdb#146580 Epic: CRDB-42942 Release note: none
Added coverage for `CREATE TRIGGER` and `DROP TRIGGER` to the Random Schema Changer Workload. Fixes: cockroachdb#146580 Epic: CRDB-42942 Release note: none
Uh oh!
There was an error while loading. Please reload this page.
We should add Triggers to the random schema workload so we can test cross interaction with other DDL features.
Jira issue: CRDB-50606
Epic CRDB-42942
The text was updated successfully, but these errors were encountered: