-
Notifications
You must be signed in to change notification settings - Fork 0
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
QueryResultRow
does not instantiate the row data
#4
Labels
bug
Something isn't working
Comments
Perhaps this will help with solution https://stackoverflow.com/questions/21024224/fetch-an-entire-row-with-jdbc-as-a-list |
benedeki
added a commit
that referenced
this issue
Aug 16, 2024
benedeki
added a commit
that referenced
this issue
Aug 16, 2024
* `QueryResultRow` is now instantiated, so can be used even after connection close * `JsonBString` deprecated, replaced by `SimpleJsonString` * setup for separation of unit and integration tests * integration tests database setup * github build action enhanced to support integration tests
benedeki
added a commit
that referenced
this issue
Aug 26, 2024
* `QueryResultRow` is now instantiated, so can be used even after connection close * `JsonBString` deprecated, replaced by `SimpleJsonString` * setup for separation of unit and integration tests * integration tests database setup * github build action enhanced to support integration tests --------- Co-authored-by: Ladislav Sulak <laco.sulak@gmail.com>
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in CPS small repos project
Aug 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
QueryResultRow
does not instantiate the row data, instead it just references the mutable JDBCResultSet
. That can be moved away from the expected row or closed completely.To Reproduce
Returned data from
DBTable.insert
cannot be retrieved.Expected behavior
Instantiate the row data, so working with the iterator is safer (also can safely use
toList
)The text was updated successfully, but these errors were encountered: