Resolve fetchall() does not return error even though the select statement should hit SQL0137N error#987
Merged
bimalkjha merged 1 commit intoibmdb:masterfrom Jan 28, 2025
Conversation
Signed-off-by: Balram Choudhary <bchoudhary@rocketsoftware.com>
bimalkjha
approved these changes
Jan 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolved issue for fetchall() does not return error even though the select statement should hit SQL0137N error.
for the CRM - https://jira.rocketsoftware.com/browse/DBC-16605
This update modifies the behavior of the fetchall() method in the ibm_db_dbi module. From now on, if there is an error in any of the rows during the fetch operation, the method will raise an error instead of returning a list of rows that do not have any errors. This change ensures that any issues encountered while fetching data are promptly raised, rather than silently skipping over problematic rows.