-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for versioned optimistic locking a la DynamoDBMapper #228
Labels
Comments
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 18, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 18, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 18, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 18, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 31, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 31, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Jul 31, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Aug 3, 2019
ezmuller
pushed a commit
to ermul/PynamoDB
that referenced
this issue
Aug 4, 2019
Should this be closed? I believe this capability was merged in via: #664 |
Thanks, this was indeed merged :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use a version attribute like DynamoDBMapper does to ensure that the record being updated hasn't changed server-side since last accessed by the client:
The text was updated successfully, but these errors were encountered: