-
Notifications
You must be signed in to change notification settings - Fork 71
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
crash on close() without rollback/commit #77
Comments
cursor must always be closed... |
@braian87b , I was closing the cursor and the connection. But it is not enough, the connection must have a rollback/commit call before close. |
Please post a small snippet to test and replicate your problem, thanks. |
Previous definition of close_SQL_connection is not enough when closing Win SQL Server connections. It must be like this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, just to report that when closing Win SQL Server connections, even just using cursor to perform retrieval Selects, the following error is generated:
To fix it, a rollback() is necessary before closing the connection. Perhaps this fix should be harcoded inside the close method is no "editing" operation was perfomed:
The text was updated successfully, but these errors were encountered: