@AndriySvyryd:
You said: [Outer transactions aren't supported because when an operation that is part of an existing transaction fails then the transaction is rolled back...]. If I understand correctly the connection reliability problem, it shouldn't affect the current transaction except the case when the DB correctly processed the request, but the response was lost. This case should be equally rare in cloud and LAN environments.
My question is: what problems you expect if I suppress existing transaction test and remove TimeoutException from ShouldRetryOn logic?
↧