Skip to content
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

go/libraries/doltcore/sqle/cluster: Replicate DROP DATABASE statements so that a dropped database is also dropped on replicas. #6754

Merged
merged 4 commits into from
Oct 2, 2023

Conversation

reltuk
Copy link
Contributor

@reltuk reltuk commented Sep 29, 2023

No description provided.

@reltuk reltuk marked this pull request as ready for review September 29, 2023 21:18
@reltuk reltuk requested a review from zachmu September 29, 2023 21:18
Copy link
Member

@zachmu zachmu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DropDatabaseProvider is an unfortunate name, otherwise LGTM!

@@ -38,6 +40,8 @@ type replicationServiceServer struct {

branchControl BranchControlPersistence
branchControlFilesys filesys.Filesys

dropDatabaseProvider func(context.Context, string) error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunate name since databaseProvider has a well established meaning

Maybe dropDatabaseHandler

@@ -94,6 +96,8 @@ type Controller struct {
branchControlController *branch_control.Controller
branchControlFilesys filesys.Filesys
bcReplication *branchControlReplication

dropDatabaseProvider func(context.Context, string) error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment about name

@reltuk reltuk merged commit 44abb30 into main Oct 2, 2023
17 checks passed
@Hydrocharged Hydrocharged deleted the aaron/replicate-drop-database branch February 7, 2024 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants