Back
[SOLVED] Transactions workaround
Hi, it is a way in version 1.3.1 to manually make transactions (start, commit, rollback) in a function code? Maybe accessing to db-connection object and using it. I need this until the official appwrite transactions are released.
TL;DR
Title: [SOLVED] Workaround for Transactions
- User asks about transaction isolation level in Appwrite
- User suggests using repeatable read to prevent cache sync issues
- Another user explains that manual rollback would be required without built-in rollback functionality
- User asks if manual transactions are possible in version 1.3.1
Solution: User can manually implement transactions by accessing the db-connection object until the official Appwrite transactions are released. 
Not really. You would have to manually implement the rollback by deleting newly created documents or updating documents to the previous state.
Yeah I think that is required because the cache will get out of sync.
Do you know what transaction isolation level appwrite will be using when the feature is ready? if I'm right the default is repeatable read https://mariadb.com/kb/en/transactions/
I'm not sure
[SOLVED] Transactions workaround
thank you we will be waiting for transaction <:appwriterocket:823996226894692403>
