New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection resiliency [DNET668] #622
Comments
Modified by: @cincuranet |
Commented by: @luronumen This issue is still reproducible on http://ADO.NET Provider v.5.0.5.0! Best Regards, |
Commented by: @cincuranet Propose some implementation in list and let's start the discussion. |
Commented by: @luronumen Hi Jiri, I think that we already have the solution once that this issue was introduced on v4.6.0.0 and this issue was not reproducible on http://ADO.NET Provider v.4.5.2.0. Best Regards, |
Commented by: @cincuranet That implementation had nothing to do with connection resiliency. |
Commented by: @luronumen Well, I was talking about the related issue DNET585 of this "New feature" issue. |
Modified by: @cincuranet |
Modified by: @cincuranet |
Modified by: @cincuranet |
Modified by: @cincuranet |
Commented by: @cincuranet Replaced by DNET818. *Generic* connection resiliency is not possible on the library level. |
Submitted by: @cincuranet
Relate to DNET585
Relate to DNET678
Relate to DNET591
Is related to DNET807
Is replaced by DNET818
Votes: 3
The text was updated successfully, but these errors were encountered: