Mandatory transactions

[john8329]

Hi, and thanks for this code, I'm trying to modify it and improve the implementation a bit for my use. One thing I noticed is that the Gateway always checks for open transactions while executing commands. This forces the developer to always open a Tx object when working with the sql.DB. It seems weird to me, is there a reason why this design choice was made? Shouldn't it be better to support self-contained statements that execute without transactions?

Thanks

[freeekanayaka]

Hi, the reason is basically that he Raft-based replication that this code was meant to support requires everything to happen in a transaction, and to only have only at most one write transaction active at time.

What is your use case?

At the moment this Go package is pretty much deprecated, since we've switched to a totally different implementation, because grpc turned out to be kind of slow for this kind of low-level APIs.

Feel free to to whatever modification you need, and I can probably merge it.

[john8329]

The use case is to have application modules that refer to a central broker for database connections. The modules are loaded as separate processes to avoid crashing the server, so they communicate via gRPC. Also I'm going to use it to implement an odbc-to-sql bridge for a platform that offers no better alternative.

Just for curiosity, what alternative did you choose? I think I'll stick with grpc for now, but just to get some insights.

Thanks