-
Notifications
You must be signed in to change notification settings - Fork 943
fix: improve error message when deleting organization with resources #17049
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
Merged
brettkolodny
merged 13 commits into
main
from
brett-66783/clarify-language-in-server-error-returne
Mar 25, 2025
Merged
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
b30a486
feat: update protect_deleting_organization function
brettkolodny cc1c564
fix: update querier test
brettkolodny 2711ded
feat: add org resources query
brettkolodny e94e7c9
feat: implement dbauthz and dbmem for new query
brettkolodny d193edd
feat: add dbauthz test for new query
brettkolodny 5c0fb09
fix: remove unused variable
brettkolodny 9645382
feat: construct and return user fiendly error when org delete fails
brettkolodny 4cfd54c
fix: change permissions
brettkolodny 8fd0740
fix: consistent spacing in sql migrations
brettkolodny a24364f
Merge branch 'main' into brett-66783/clarify-language-in-server-error…
brettkolodny b84d70e
fix: migration numbers
brettkolodny 27320c8
fix: dump
brettkolodny d17e29f
fix: migration numbers
brettkolodny File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
fix: consistent spacing in sql migrations
- Loading branch information
commit 8fd074043a40a88810f45d61b65b84ff91daa7ec
There are no files selected for viewing
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
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and this file also has inconsistent indentation throughout. we're really not usually picky about sql formatting, but sticking with a consistent indentation character/width is nice. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks like right now your down migration is just a copy of your up migration.
I think your down migration really only needs to be
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I think there were some copy paste errors as I changed from another branch to this one (long story). Probably also why there is the tabs vs spaces issue.
The down migration can't just be dropping the function since the function already exists, as far as I understand I'd have to re-declare the original function from a previous migration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually taking a closer look now the down migration is correct, or at least what I meant it to be. In it we drop the existing functions and triggers and re-create the old one from migration 296