Can you provide an update on this feature (particular SQL participating in transactions)?
I can't figure out by the roadmap, issues for 3.0, or the 3.0 documentation whether SQL can be participate in a transaction along side the graph api. On Thursday, July 14, 2016 at 2:22:17 AM UTC-4, Luigi Dell'Aquila wrote: > > Hi, > > This is our intention, so the answer is "it's very likely, but not yet > implemented, even in alpha" > > Thanks > > Luigi > > > 2016-07-14 0:41 GMT+02:00 odbuser <[email protected] <javascript:>>: > >> Bump... this one is very important for anyone using transactions. Any >> comments? >> >> >> On Tuesday, June 21, 2016 at 10:05:47 PM UTC-4, odbuser wrote: >>> >>> Are the SQL and JS query/commands really going to participate in >>> transactions in 3.0? According the docs, this is the case but is it so? >>> Can you provide the links to the issues in git that will resolve this >>> issue? I'm interested in how this will work... especially select >>> statements executed during a transaction. >>> >>> http://orientdb.com/docs/last/Transactions.html >>> >>> "In this scenario you can have different isolation levels with commands. >>> This issue will be solved with OrientDB v3.0 where the transaction will be >>> flushed to the server before to execute the command." >>> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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.
