Gary Donovan 802402bdba 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
2018-07-13 10:11:10 +01:00
..
2018-04-13 10:37:06 -04:00
2017-10-22 21:36:39 +01:00
2018-04-04 00:28:39 -07:00
2017-05-10 21:58:42 -04:00
2017-02-23 21:37:43 -05:00
2018-05-09 09:20:48 +02:00
2017-09-27 09:54:46 +01:00
2017-06-20 11:58:18 -07:00
2018-06-09 23:42:33 -07:00
2017-02-23 21:37:43 -05:00
2017-10-16 17:06:22 -07:00
2017-02-15 22:35:45 -05:00
2017-02-23 21:37:43 -05:00
2017-02-23 21:37:43 -05:00