Correct odbc:row() type specification#10678
Merged
IngelaAndin merged 1 commit intoerlang:maintfrom Feb 18, 2026
Merged
Conversation
The `odbc:row()` type does not currently account for cases where application code sets the `tuple_row` option to `off` when opening a database connection. This in effect causes Dialyzer to emit incorrect warnings for the application code.
Contributor
CT Test Results 2 files 15 suites 5m 13s ⏱️ Results for commit fb18196. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
IngelaAndin
approved these changes
Feb 18, 2026
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
3 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.
The
odbc:row()type does not currently account for cases where application code sets thetuple_rowoption tooffwhen opening a database connection. This in effect causes Dialyzer to emit incorrect warnings for the application code.