Closed numberoverzero closed 9 years ago
This is a good start, but it's incomplete. I think that all parts of the code that interface with dynamo3 will have to be changed, and we'll need to add a lot of tests to make sure these fields work for everything. For example, if you try to atomically increment an aliased field model.incr_(field_name=2)
, it will do the wrong thing.
Implements most of #16 (doesn't handle conflicts)
attribute_name, if defined, will be used as the column name in AWS DynamoDB, while the field will still be bound to the model by its name. For example:
The table for this model in AWS DynamoDB would have hash key 'f'.