-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Why do I call Dynamoid::TransactionWrite and get an error name uninitialized constant? #763
Comments
I thought I remembered the first version of TransactionWrite being released in 3.10 but I don't see it there. It's in main so you can put this in your gemfile: This branch has some more documentation about some hidden features but won't be live until the non-transaction actions catch up: @andrykonchin Want to release transactions some time? |
|
@ckhsponge Let me ask, if I want to |
No. I believe in DynamoDB deletions can only occur individually, in a batch or in a transaction and always require primary keys. Dynamoid's delete_all probably gets keys and deletes in batches and this wouldn't be possible in a transaction. |
@ckhsponge Yeah, the next version with transactions support should be released soon. I have some ideas how to polish new tests and wanted to close some minor issues. |
@andrykonchin Is there any plan for when the next release will take shape? Happy Friday! |
Yeah, I am going to spent some time soon to polish recent changes and prepare the release. |
Why do I call Dynamoid::TransactionWrite and get an error name uninitialized constant?
Please help me, thankssss <3
The text was updated successfully, but these errors were encountered: