fornwall opened a new pull request, #5023:
URL: https://github.com/apache/arrow-adbc/pull/5023

   `AdbcStatement.close()` decremented the connection's open-statement count 
before checking whether the statement was already released, so a second close() 
miscounted.
   
   This does not need an explicit double close: if releasing the statement 
fails (e.g. the server is gone) or is interrupted, the dbapi `Cursor` stays 
unclosed, and `Connection.close()` and `Cursor.__del__` close it again.
   
   That raised "Underflow in closing this AdbcStatement" or, with another 
cursor open, released the connection while that cursor's statement was still 
open.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to