feat(dashboards): loosen unique title db constraint on dashboards#104046
Merged
DominikB2014 merged 2 commits intomasterfrom Nov 26, 2025
Conversation
edwardgou-sentry
approved these changes
Nov 26, 2025
Contributor
|
This PR has a migration; here is the generated SQL for for --
-- Alter unique_together for dashboard (0 constraint(s))
--
ALTER TABLE "sentry_dashboard" DROP CONSTRAINT "sentry_dashboard_organization_id_title_6ca343f8_uniq";
--
-- Create constraint sentry_dashboard_organization_title_uniq on model dashboard
--
CREATE UNIQUE INDEX CONCURRENTLY "sentry_dashboard_organization_title_uniq" ON "sentry_dashboard" ("organization_id", "title") WHERE "prebuilt_id" IS NULL; |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This updates the unique title constraint to only apply for non-prebuilt dashboards. This allows us to built prebuilt ones with the same title as an existing user created on. The UI will distinguish the two by the author field