Tweak comparison to treat NULL/NOT_NULL correctly. (#1709)
The AWS documentation says that a ComparisonOperator of NULL means the attribute should not exist, whereas NOT_NULL means that the attribute should exist. It explicitly says that an attribute with a value of NULL is considered to exist, which contradicts our previous implementation. This affects both put_item and get_item in dynamodb2. https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Condition.html
This commit is contained in:
parent
7d201c48b5
commit
802402bdba
4 changed files with 107 additions and 12 deletions
1
.gitignore
vendored
1
.gitignore
vendored
|
|
@ -14,4 +14,5 @@ build/
|
|||
python_env
|
||||
.ropeproject/
|
||||
.pytest_cache/
|
||||
venv/
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue