Optimize BigDecimal zero value handling to reduce memory footprint #117
+5
−0
Conversation
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
…e memory footprint
|
Hi, thank you for your contribution. Please confirm this code is submitted under the terms of the OCA (Oracle's Contribution Agreement) you have previously signed by cutting and pasting the following text as a comment: |
|
I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it. |
|
Hi, thank you for your contribution. Your code has been assigned to an internal queue. Please follow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was done:
When using MySQL JDBC driver to process result sets containing BigDecimal values (including zero values), the application retrieves numeric fields that evaluate to 0 (e.g., SELECT amount FROM orders WHERE amount = 0).
What was expected:
Following the behavior of the Oracle JDBC driver, which reuses the same
BigDecimalinstance for zero values to minimize memory allocation and optimize memory footprint. This ensures consistent reference equality (i.e.,object1 == object2for zero values) and reduces redundant object creation.What actually happened:
The MySQL JDBC driver creates a new BigDecimal instance for each zero value encountered in the result set, even when the value is logically identical to BigDecimal.ZERO.