Transactions in integration libraries for various languages

[gaurav-bagga]

There is documentation for transaction available here which gives brief idea how transactions can be managed. However looking into integration libraries primarily for Rust and Java it is not clear how transaction can be started, committed or rollbacked using client API.

For instance the Rust API as described here there is no method to start transaction, commit or rollback.

Coming from Java background. I was expecting something where methods are provided to start, commit, rollback. Now Rust is using async model, which I deem is quite similar to coroutines in Kotlin (an assumption). There needs to be transaction context which is passed around suspend/resume points, similar to what we have in Rust async/await. As a piece of code is not bound to run on same thread as what happens in Kotlin mostly (you could confine it to a thread but that would defeat lot of purpose, I am assuming again something similar happens in Rust), thread locals are no good.

I'll really appreciate if some advice is provided how to deal with transactions using API or should I send a batch as string as follows.

BEGIN TRANSACTION;
-- Setup accounts
CREATE account:one SET balance = 135,605.16;
CREATE account:two SET balance = 91,031.31;
-- Move money
UPDATE account:one SET balance += 300.00;
UPDATE account:two SET balance -= 300.00;
-- Finalise
COMMIT TRANSACTION;

to the API call db.query(sql) for now.

I have just started with Rust and Surrealdb so my lookout of API might be biased with my background in Java.
Just need some insights.

Thanks, can't deny Surrealdb is awesome and fun to work.

[gaurav-bagga]

To add to above question. I was thinking of an use case as follows.

1. I create a record locally in surrealDb.
2. I have to sync this record over a REST API with third party which could fail.
3. If all goes good I commit else rollback.

[jacek-kurlit]

I have the same issue, is there any answer to it?

[farzadbekran]

Someone answer please? This is important. I'm writing a driver for Haskell, I need to know if this will eventually be possible or it will never be implemented.

[Davidc2525]

you should directly use tikv instead of surrealdb for concurrent transaction management

[farzadbekran]

Maybe I'm missing something but doesn't that mean I lose all the functionality of SurrealDB? What's the point of using SurrealDB if I have to drop it's functionality to have transactions?

[Davidc2525]

Exactly, there is no reason to use surreal, although you can use it in everything else and not in parts where you need a transaction. I decided not to use surrealdb, I feel that not giving answers to these types of questions from the community is a lack of seriousness.

[Davidc2525]

The truth is that it is a poor implementation and without giving answers for anything I found myself having to search, needing a db that handles concurrent transactions well, it is better to use tikv directly and optionally tiDB