You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What was implemented is a context independent of a transaction. It seems it is better this way so then code can use context that can encompass transactions.
If context is co-dependent w/ a transaction, then you can't use same context across different transactions. Of course, there are advantages on "concurrency & resource locking" between these two approaches. BUT at end of it, it was voted that the ability to use one context across 1 to many transactions is a great feature we don't want to lose.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What was implemented is a context independent of a transaction. It seems it is better this way so then code can use context that can encompass transactions.
If context is co-dependent w/ a transaction, then you can't use same context across different transactions. Of course, there are advantages on "concurrency & resource locking" between these two approaches. BUT at end of it, it was voted that the ability to use one context across 1 to many transactions is a great feature we don't want to lose.
So, we retain it. :)
All reactions