Implement wasNull tracking in ResultSet getter methods #3838
+370
−52
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.
Summary
Implemented comprehensive wasNull tracking and refactored getter methods in JDBC4ResultSet to ensure JDBC specification compliance and improve code maintainability.
Changes
Added wasNull tracking to all getter methods: Covers primitive types, objects, dates/times, streams, and BigDecimal
Refactored columnLabel getters to use delegation pattern: Eliminates code duplication and ensures consistent wasNull behavior
Bug Fixes & Code Quality
Testing
Added comprehensive tests for wasNull tracking, columnLabel getters, stream methods, and null handling