An example of a transactional request about go-driver HOT 13 CLOSED

Look in the tests https://github.com/arangodb/go-driver/blob/master/test/database_transaction_test.go

from go-driver.

@ewoutp this is not bearable. Arangodb looked so promising and then this.

Who wants to write transaction in javascript in form of a string when you are familiar with PHP, Go or even Javascript? The other downside is that you can't interact with your business logic or other services. Neo4j provides one query language to update, query nodes and edges. If you want to start a transaction you can do it via multiple cypher querys over HTTP or Bolt. I really don't understand why Arangodb took this path.

The other point is that arangodb is not capable to provide full ACID support on queries with multiple documents here the whole transaction feature feels like marketing joke but I hope you will rock it. Arangodb is still a great product.

from go-driver.

@ewoutp Now that v3.5 has introduced stream transactions, will this feature be added to the go driver?

from go-driver.

I'm a little bit confused after looking at the tests. So, yes, "action" parameter is a string, which is a JavaScript closure.

Can anyone explain how I'm supposed to integrate this into my app? Am I supposed to construct a JavaScript code in Go now? What if I have a business logic spread across multiple services/classes (reading and writing into different collections), how do I consolidate it all in a JavaScript string?

from go-driver.

Yep, seem so https://github.com/arangodb/go-driver/blob/master/database.go#L58 It looks like that only javascript is supported but this is documented here https://docs.arangodb.com/3.3/Manual/Transactions/TransactionInvocation.html#execute-transaction

I'm a little bit confused too. Aren't we able to write transaction with the language and tools of the client driver? Hacking this in javascript is cool but the tooling is very bad. We receive no instant feedback when we write code and debugging is hard. What's the big deal with this?

from go-driver.

I'm a bit sad to say that for now the answer is yes. You have to write your transaction in JS and pass that as a Go string to the driver.
The reason for that is that the ArangoDB API (see docs link mentioned above) supports transactions in JS only. This enables the server (or cluster) to re-execute the entire transaction automatically if it needs to retry for whatever reason).
We hope to support a more traditional style of transaction in the future with an all-Go solution.

from go-driver.

from go-driver.

@weinberger I think there is no misunderstanding here. It's clear that AQL is transactional. In the mean time, number of cases when multi query transaction is needed is significant large. Unfortunately, being forced to write business logic in JS while using Go is not sustainable.

from go-driver.

from go-driver.

Understood, and thank you for letting me know.
What do you suggest @weinberger? Do you want me keep the ticket open or should I close it?

from go-driver.

@vanobig I'm closing the issue now. Feel free to re-open if needed

from go-driver.

Is there any chance to get a multi query example with a transaction in the documentation? How has the javascript query look like to commit or rollback the transaction?

Cheers sandro

from go-driver.

I can see that there are methods BeginTransaction, CommitTransaction and AbortTransaction.
But there is no documentation anywhere that I could find.

How am I supposed to use those functions? Am I supposed to use those functions?

from go-driver.