Skip to content
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: query could hang transaction if ResultSet#next() is not called #643

Merged
merged 1 commit into from Nov 18, 2020
Merged

fix: query could hang transaction if ResultSet#next() is not called #643

merged 1 commit into from Nov 18, 2020

Commits on Nov 17, 2020

  1. fix: query could hang transaction if ResultSet#next() is not called 

    If the first statement of a read/write transaction was a query or a read operation,
and the application would not call ResultSet#next() on the return result, the transaction
would hang indefinetely as the query would be marked as the one that should initiate the
transaction (inline the BeginTransaction option). The query would however never be
executed, as the actual query execution is deferred until the first call to ResultSet#next().

Fixes #641
    @olavloite
    olavloite committed Nov 17, 2020
    Copy the full SHA
    39a3a85 View commit details
    Browse the repository at this point in the history