Remove UpdateColumns#19
Merged
jsha merged 1 commit intoJun 11, 2026
Merged
Conversation
aarongable
approved these changes
Jun 11, 2026
jsha
approved these changes
Jun 11, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #15.
This removes the unused
UpdateColumnsAPI and the relatedColumnFilterplumbing. Boulder does not use this API, and removing it avoids preserving the cached filtered-update behavior reported in #15.The change deletes
DbMap.UpdateColumns,Transaction.UpdateColumns,ColumnFilter, the internal filtered update path, and the column-filter test/helper.Verification:
go test . -count=1go test ./... -count=1go vet ./...go test -race ./... -count=1git diff --checkI also checked Boulder application code for
UpdateColumns/ColumnFilter; the only hits were in Boulder’s vendored borp copy.