Support NE condition operator

[andrykonchin]

Now we can use ne operator in where conditions:

Document.where('age.ne' => 10).all

Be aware it doesn't work for sort key in QUERY operation (when there is some condition on partition key)

https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Condition.html

Related issue #241

[coveralls]

Coverage increased (+0.005%) to 97.542% when pulling a82e881 on add-ne-operator into 46b1784 on master.

[coveralls]

Coverage increased (+0.005%) to 97.542% when pulling a82e881 on add-ne-operator into 46b1784 on master.

[coveralls]

Coverage increased (+0.005%) to 97.542% when pulling a82e881 on add-ne-operator into 46b1784 on master.

[coveralls]

Coverage increased (+0.005%) to 97.542% when pulling a82e881 on add-ne-operator into 46b1784 on master.

[pboling]

Awesome!

[pboling]

@andrykonchin We need to add the synopsis of all these changes into the CHANGELOG!

[mrkamel]

can this query be supported by indices?
i have a global secondary index on version, but dynamoid complains:

pry> Recommendation.where('version.ne': '8a76c71b52b928ed12f5268ed8291d0b').first
Queries without an index are forced to use scan and are generally much slower than indexed queries!
You can index this query by adding index declaration to recommendation.rb:
* global_secondary_index hash_key: 'some-name', range_key: 'some-another-name'
* local_secondary_index range_key: 'some-name'
Not indexed attributes: :version.ne

[andrykonchin]

What request would you expect Dynamoid to perform in terms of Scan/Query operations?

[mrkamel]

@andrykonchin yeah, ok, it seems there is no dynamo query which uses the key together with a NE operation. I was just wondering about the message "Not indexed attributes 'version.ne'" and thought there'd be something wrong. But i see, thx.