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.

Sign up for GitHub

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

Jump to bottom

Fix pyodbc.ProgrammingError: Attempt to use a closed connection. #382

Merged

jettify merged 1 commit into aio-libs:master from duh386:fix_programmingerror_on_closed_pool

Mar 16, 2023

Contributor

duh386 commented Nov 16, 2022 •

edited

What do these changes do?

Fix pyodbc.ProgrammingError in case of trying to close a connection, which was already closed

Are there changes in behavior for the user?

No

Related issue number

Checklist

I think the code is well written
Unit tests for the changes exist - no tests required
Documentation reflects the changes - no changes required
Add a new news fragment into the CHANGES folder
- name it <issue_id>.<type> (e.g. 588.bugfix)
- if you don't have an issue_id change it to the pr id after creating the PR
- ensure type is one of the following:
  - .feature: Signifying a new feature.
  - .bugfix: Signifying a bug fix.
  - .doc: Signifying a documentation improvement.
  - .removal: Signifying a deprecation or removal of public API.
  - .misc: A ticket has been closed, but it is not of interest to users.
- Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.


          Fix pyodbc.ProgrammingError: Attempt to use a closed connection.

ac4f866

jettify approved these changes

View reviewed changes

jettify merged commit 6e29112 into aio-libs:master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment