-
Notifications
You must be signed in to change notification settings - Fork 966
Cog 414 fix postgres database deletion #163
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
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ee2f1fb
fix: Add deletion of all tables in all schemas for postgres
dexters1 c1c0dc4
fix: Resolve issue with database deletion
dexters1 36377c0
fix: Move cleaning of MetaData out of drop table loop
dexters1 c67639f
refactor: Remove unnecessary print statement
dexters1 ddaa1e8
fix: Fix table deletion for SqlAlchemyAdapter
dexters1 09f5fa8
feat: Add deletion by id for SqlAlchemyAdapter
dexters1 dc8680f
fix: Add support for postgresql syntax for getting table function in …
dexters1 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
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
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.
🛠️ Refactor suggestion
Consider dropping entire schemas instead of individual tables
Currently, the
delete_databasemethod iterates over each table within each schema and drops them individually. This can be inefficient, especially if there are many tables or other objects within the schemas. Dropping the entire schema in a single operation is more efficient and ensures that all objects within the schema are removed.Apply this diff to simplify the database deletion process:
This modification:
DROP SCHEMAcommand with theCASCADEoption, which removes the schema and all dependent objects.📝 Committable suggestion