fix(applier): added support for unique text column, they are mapped to uint8[] #1583
Conversation
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
markmarkmarkthebest
requested review from
meiji163,
rashiq and
timvaillancourt
as code owners
Contributor
Author
|
I can check if the go type of the column is uint8[] first and handle that case specifically if needed |
meiji163
approved these changes
Sep 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Related issue: #1582
Description
This PR changes the
updateModifiesUniqueKeyColumnsfunction inapplier.goto usereflect.DeepEqualfor value comparison to handle unique keys that are text fields because they are mapped to unit8[] slices.