We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The logic in DefaultDiagnosticsContext::resultSetFetchedRows alters the underlying ResultSet in order to calculate the actual fetched rows:
DefaultDiagnosticsContext::resultSetFetchedRows
ResultSet
public final int resultSetFetchedRows() { if (resultSet == null) return -1; try { if (resultSetClosing || resultSet.getType() != ResultSet.TYPE_FORWARD_ONLY) { while (resultSet.next()) resultSetFetchedRows++; resultSet.absolute(resultSetConsumedRows); } } catch (SQLException ignore) {} return resultSetFetchedRows; }
This means that one DiagnosticsListener querying this value might affect the result of this method for other listeners later on.
DiagnosticsListener
The text was updated successfully, but these errors were encountered:
This was discovered as the LoggingDiagnosticsListener created a regression: #14146
LoggingDiagnosticsListener
Sorry, something went wrong.
[#14191] DefaultDiagnosticsContext should cache resultSetFetchedRows
7c6ab54
Fixed in jOOQ 3.18.0, 3.17.6 (#14192), and 3.16.12 (#14193)
[#14191] DefaultDiagnosticsContext should cache
dc3ca9e
resultSetFetchedRows
7e18b61
No branches or pull requests
The logic in
DefaultDiagnosticsContext::resultSetFetchedRows
alters the underlyingResultSet
in order to calculate the actual fetched rows:This means that one
DiagnosticsListener
querying this value might affect the result of this method for other listeners later on.The text was updated successfully, but these errors were encountered: