Skip to content
Start project
Back

[SOLVED] Transactions workaround

  • 0
  • Resolved
  • Databases
View on Discord
danilo73
15 Apr, 2023, 14:04

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.
Drake
15 Apr, 2023, 14:51

Not really. You would have to manually implement the rollback by deleting newly created documents or updating documents to the previous state.

danilo73
15 Apr, 2023, 15:11

Yeah I think that is required because the cache will get out of sync.

danilo73
15 Apr, 2023, 15:16

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/

Drake
15 Apr, 2023, 15:17

I'm not sure

danilo73
15 Apr, 2023, 15:17

[SOLVED] Transactions workaround

danilo73
15 Apr, 2023, 15:18

thank you we will be waiting for transaction <:appwriterocket:823996226894692403>

Reply

Reply to this thread by joining our Discord

Reply on Discord

Recommended threads

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more