Will SQL and JS be in transactions in v3.0?

[odbuser]

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

[odbuser]

Bump... this one is very important for anyone using transactions.  Any comments?

[Luigi Dell'Aquila]

Hi,

This is our intention, so the answer is "it's very likely, but not yet implemented, even in alpha"

Thanks

Luigi

--

---
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 orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[odbuser]

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.

[Luigi Dell'Aquila]

Hi,

Here's a quick update. V 3.0 M1 (alpha) will be released in a few days with some important notes. It's not feature complete yet, but it will include (among other things) two important improvements:

- the new SQL engine: we changed a little bit the query APIs and completely rewrote the internal mechanisms of execution planning and query execution. The query parser is the same as the strict parser of v 2.2, so the language is the same, apart from some small changes and additions (eg. now we have a DISTINCT keyword for projections)

- remote transactions: until v 2.2 all the transactions were executed on the client and transferred to the server only at commit time, so any SQL statement during a transaction was executed on the server and outside of the transaction itself. In V 3.0 we added management of remote transactions: tx are still executed on the client, but as soon as an SQL statement is executed, the transaction is flushed to the server (not yet committed of course), so the SQL statement will run inside current transaction.

So the answer to your original question is finally YES, in 3.0 we will have remote transactions, SQL inside transactions and a consistent behavior of remote and plocal instances.

About details and docs, many things will be updated in next few days and released with the M1

Thanks!

Luigi

To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscribe@googlegroups.com.

[odbuser]

Has any of this happened?  I haven't seen any general announcement, release notes, details, or updates to docs.

[Luigi Dell'Aquila]

Hi,

Not yet, it resulted to be longer than expected, but we are working to release it soon

Thanks

Luigi

--

[odbuser]

Thanks for the response.  I'll do my best to test out the new features and provide feedback when available.

On Monday, March 6, 2017 at 3:42:39 AM UTC-5, Luigi Dell'Aquila wrote:

Hi,

Not yet, it resulted to be longer than expected, but we are working to release it soon

Thanks

Luigi

2017-03-03 20:28 GMT+01:00 odbuser <odbu...@gmail.com>:

Has any of this happened?  I haven't seen any general announcement, release notes, details, or updates to docs.

On Monday, January 23, 2017 at 3:51:54 AM UTC-5, Luigi Dell'Aquila wrote:

About details and docs, many things will be updated in next few days and released with the M1

--

---
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 orient-databa...@googlegroups.com.