return-txn-current-if-exists

[brucecurcio]

No description provided.

[akleinib]

Are these changes still prevent scenarios like:

1. Caller requested a R-O transaction first then requests a R/W transaction,
2. Caller requested a R-O transaction with isolation level A first then requests a R-O transaction with isolation level B,
3. ...

?

For those cases we shouldn't return the current transaction if the newly requested transaction doesn't match the characteristics of the existing one.

[brucecurcio]

Are these changes still prevent scenarios like:

1. Caller requested a R-O transaction first then requests a R/W transaction,
2. Caller requested a R-O transaction with isolation level A first then requests a R-O transaction with isolation level B,
3. ...

?

For those cases we shouldn't return the current transaction if the newly requested transaction doesn't match the characteristics of the existing one.

as discussed, i put in a check that prevents attempts to change from RO DB to RW DB but returns the existing db txn in all other cases.