Just a quick question to see if there are plans to offer a more robust transaction model than what is currently available.
I need to be able to initiate a transaction and then associate multiple database activities with that transaction, and then later perform an explicit Commit or Rollback. I can't just throw everything into javascript and push it to arango to manage - my middle tier components have complex and distributed business logic elements that I simply cannot reproduce into javascript equivalents. The only solution is to ask arango to initiate a transaction, and then associate my mid-tier data calls to that open transaction until all the processing is completed successfully, and then explicitly call COMMIT or ROLLBACK. The current (v3) transaction model is one of ArangoDB's greatest weaknesses, IMO, as it means I cannot build a robust middle tier layer with any true means of data consistency guarantees. Building a software layer to author complex javacript at runtime to pass off to the database engine, isn't really a viable solution. Please advise. Thanks Bill -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
