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).
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 -- 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.
