Persistence Refactors for Nil Handling #28
Merged
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.
This change covers a few different areas related to our persistence
logic:
Aws::DynamoDB::Client#update_item
now use updateexpressions exclusively.
nil
values will not be persisted in any case unless:persist_nil
is set for the attribute(s) in question. There are also
collection-specific parameters to persist nil as empty collections in
some cases, which are now honored.
REMOVE
expression when the value isnil
and:persist_nil
isfalse
for the attribute.