catalin/moto
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Tweak comparison to treat NULL/NOT_NULL correctly. (#1709)

Browse source 
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:
Gary Donovan 2018-07-13 19:11:10 +10:00 • committed by Terry Cain
commit 802402bdba
4 changed files with 107 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

6
moto/dynamodb2/comparisons.py
View file

@ -29,8 +29,10 @@ COMPARISON_FUNCS = {
'GT': GT_FUNCTION,
'>': GT_FUNCTION,
'NULL': lambda item_value: item_value is None,
'NOT_NULL': lambda item_value: item_value is not None,
# NULL means the value should not exist at all
'NULL': lambda item_value: False,
# NOT_NULL means the value merely has to exist, and values of None are valid
'NOT_NULL': lambda item_value: True,
'CONTAINS': lambda item_value, test_value: test_value in item_value,
'NOT_CONTAINS': lambda item_value, test_value: test_value not in item_value,
'BEGINS_WITH': lambda item_value, test_value: item_value.startswith(test_value),