Repository navigation
docs: add a transactions reference to the Resources lists - #592
Open
dynotable-user wants to merge 2 commits into
Open
dynotable-user wants to merge 2 commits into
dynotable-user wants to merge 2 commits into
Conversation
✅ Deploy Preview for electrodb-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds one reference to the "links to help you understand the mechanics behind DynamoDB Transacts" list on the
transact-writeandtransact-getpages. Additive only, nothing reordered or replaced.The guide covers a couple of things the existing three references don't go into, which is why I think it earns a place rather than just lengthening the list:
CancellationReasonscode, index-aligned with the actions you sent, and what to do about each. The SDKs do not retry these for you.ConditionCheck+Update+Puton one counter is 6 units against the 1,000-per-partition ceiling, which is about 166 a second. Canceled transactions still consume capacity.[ConditionalCheckFailed, None, None].ConditionCheckcannot sit on the same item another action writes (Transaction request cannot include multiple operations on one item), and thatstatusneeds#statusbecause it is reserved.Every example in it was run against DynamoDB Local 3.3.1.
Disclosure: I work on DynoTable, a DynamoDB GUI, and the guide is on our site. It is a technical article rather than a product page, in the same shape as the dynobase.dev reference already in the list, and it does have a short section at the end about doing this in our app. Happy to drop this if you would rather the list stayed vendor-light, or to add it to only one of the two pages.