Releases: altitudenetworks/dynamoquery
Releases · altitudenetworks/dynamoquery
2.11.1
Notes
Fixed
- Revert
batch_delete_records
call in dynamo_table.clear_table
#64
2.11.0
Notes
Changed
DataTable.filter_records
: add support for not_equals
operand #60
Fixed
- Generate
DynamoTable.primary_index
dynamically to respect overriden table keys #61
- Handle
UPDATING
status in dyanmo_table.create_table
#62
2.10.1
Fixed
- Case insensitive column names bug in
DataTable.drop_duplicates
#58
2.10.0
Changed
- Ignore case in column names match in
DataTable.drop_duplicates
#56
2.9.0
Changed
- Added
DataTable.drop_duplicates
#54
2.8.0
Added
- Nested keys support for
ConditionExpression
#52
2.7.1
Fixed
- Fix missing required record keys error on internal
batch_get
usage #50
2.7.0
Added
DynamoTable.cached_batch_get
method
DynamoTable.cached_get_record
method
DynamoTable.invalidate_cache
method #48
Fixed
DynamoTable
does not use sort key if it does not exist in record
- Always use provided
DynamoQuery
subclass in DynamoTable
- Filter out non-key data from batch methods #48
2.6.0
Added
DynamoDictClass.get_required_field_names
method
DynamoDictClass.get_field_names
method #44
Fixed
DynamoTable
now works with DynamoDictClass
with required fields
DynamoDictClass
child class methods were detected as field names
DynamoDictClass
fields are initialized only once per class #44
2.5.0
Added
DynamoTable.read_capacity_units
argument
DynamoTable.write_capacity_units
argument
read_capacity_units
and write_capacity_units
arguments to DynamoTableIndex
#41
projection
argument to DynamoTableIndex
#42
Changed
DynamoTable
no longer has default provision throughput specified #41
DynamoTable.batch_upsert_record
no longer works as a generator
DynamoTable.batch_delete_record
no longer works as a generator #42