SQL, REST Transactions

[Waclaw Szymkowiak]

I tried searching on the forum and looked at the documentation but cannot find a definitive answer to the question about handling transactions in OrientDB. Please, assume my application will be in PHP - the only note I found for the connector mentions that commit() method is not supported at this point. I have no problems executing REST API calls - anything that would allow me to perform ACID transactions on several records. Is this a good example of ACID transaction (https://github.com/orientechnologies/orientdb/wiki/OrientDB-REST#wiki-example-5)? If it is, then it is very close, I guess. Assuming, that I update a numerical value in first operation (e.g. val = val + 10), can I read the result and use it within the SQL command executed later on within the transaction? What value on the first modified record will be visible to other transactions trying to access the same record? If the transaction fails, does the retry have to be taken care of on the application side? Does this work in a distributed setup?

I also found a note on "transactional" SQL keyword and an example when it's used along with a SQL query to update an edge. Is there a way to extend this behavior to wrap multiple updates?

Thanks,

V

[vaclav77]

It would certainly be nice to keep all the documentation in one place but this looks like a step in the right direction:

https://github.com/orientechnologies/orientdb/issues/2010

[Waclaw Szymkowiak]

https://github.com/orientechnologies/orientdb/issues/2010

https://github.com/orientechnologies/orientdb/issues/1056

--
 
---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/vrXNIkC36wA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.