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
Describe the problem
Some collection call paths don't respect the intended transaction scope. Haven't looked all every method yet, but in can be seen in the collection.updateWithDocID (private func), which is given a transaction in its arguments, but then makes a call to collection.Get (public func), which doesn't get a transaction. This only affects the implicit transaction that collections will create if they haven't explicity (ie: collection.WithTxn) been given one.
This is because the collection.getTxn will create a new transaction on every call unless there is an existing transaction on the collection struct.
To Reproduce
Any public Collection call which uses implicit transactions that then calls another public Collection function.
Expected behavior
All DB calls respect the implicit or explicit transaction for the entire lifecycle/scope of that call.
The text was updated successfully, but these errors were encountered:
Describe the problem
Some collection call paths don't respect the intended transaction scope. Haven't looked all every method yet, but in can be seen in the
collection.updateWithDocID
(private func), which is given a transaction in its arguments, but then makes a call tocollection.Get
(public func), which doesn't get a transaction. This only affects the implicit transaction that collections will create if they haven't explicity (ie:collection.WithTxn
) been given one.This is because the
collection.getTxn
will create a new transaction on every call unless there is an existing transaction on thecollection
struct.To Reproduce
Any public Collection call which uses implicit transactions that then calls another public Collection function.
Expected behavior
All DB calls respect the implicit or explicit transaction for the entire lifecycle/scope of that call.
The text was updated successfully, but these errors were encountered: