Don't return error on unexpected UDT field in SerializeCql macro #885
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.
In order to properly support ALTERing UDTs in database, code that serializes UDT shouldn't return error when there is column in UDT that is not present in Rust struct.
This PR changes the default behavior like this, and adds an
force_exact_match
attribute to opt-in to previous behavior.CQL specification says:
so I decided to not send anything in place of missing fields rather than send e.g. NULLs.
Pre-review checklist
./docs/source/
.Fixes:
annotations to PR description.