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

feat: track total message bandwidth #73

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

adklempner
Copy link
Collaborator

No description provided.

@adklempner adklempner force-pushed the feat/total-message-bandwidth branch from b13ed4a to 1add6e7 Compare December 4, 2024 00:53
@@ -132,6 +133,11 @@ func DropTables(db *sql.DB) {
log.Fatalf("an error '%s' was not expected when dropping the index", err)
}

_, err = tx.Exec("DROP INDEX IF EXISTS sentMessageTotal_unique")
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if it's possible later to create 0_ prefixed migration that drops all the tables that we create to avoid having to remember to add these here DROPs here 🤔

@adklempner adklempner merged commit 65c346b into master Dec 4, 2024
3 checks passed
@adklempner adklempner deleted the feat/total-message-bandwidth branch December 4, 2024 16:22
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