Hy Andreas, On Friday, June 24, 2016 at 11:57:44 AM UTC+2, Andreas Jung wrote: > > Hi there, > > first: thanks a lot for the 3.0 release of ArangoDB. This is the first > ArangoDB release that feels good enough for me to > be used in production (primarily because of the persistent indexes). > > Glad to hear!
> Question related transactions: is my assumption right that the code to be > executed as part of a transaction must > be always Javascript? From the prospective of a Python developer and > Python bindings: the transaction support > on the driver level seems to be limited either to specifiying the 'action' > code as some JS snippet on the Python level in python-arango > or limited to a particular operation (create_document, update_document) in > ArangoPy. Since there is no BEGIN...COMMIT for transactions > it would not be possible to start a transaction on the Python client, > perform some arbitrary operations through the Python API and then sending > an explicit COMMIT. Is this right? > > Andreas > Yes, transactions across more than one query are only supported inside of FOXX-services and other server side javascript. The technical foundation to offer client side transactions are on our roadmap as one of the hot topics. Now that 3.0 is out, we're going to discuss what to do in which sequence. Once we decided on that, we're going to update the publicaly available roadmap accordingly. Cheers, Willi -- 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.
