commit_operations
Commit all pending update and remove operations in a CachingTable
If there is nothing to commit, calling the commit_operations will not send any request to your databases.
Your update and remove operations are sent in separate requests to your databases.
If the size of your operations exceed the DynamoDB operations limit of 400kb, they will be sectioned and sent in multiple requests.
#
Operations considered as update :- put_record
- update_field
- update_field_return_old (will be executed right away if the value to remove is not found in the cache)
- update_multiple_fields
- update_multiple_fields_return_old (will be executed right away if the values to update are not found in the cache)
#
Operations considered as remove:- delete_record
- delete_field
- delete_multiple_fields
- remove_field (will be executed right away if the value to remove is not found in the cache)
- remove_multiple_fields (will be executed right away if the values to remove are not found in the cache)
#
Parameterscommit_operations has no parameters.
#
AvailabilityTable | Available |
---|---|
DynamoDBBasicTable | โฌ |
DynamoDBCachingTable | โ |
ExternalDynamoDBApiBasicTable | โฌ |
ExternalDynamoDBApiCachingTable | โ |