Skip to content
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

CAY-2660 BigDecimal comparision fix #428

Merged
merged 5 commits into from
Sep 11, 2020

Conversation

stariy95
Copy link
Member

BigDecimals that differ only in scale are treated as different values causing unneeded updates

stariy95 and others added 5 commits June 16, 2020 14:35
…nt values causing unneeded updates

CAY-2660 BigDecimals that differ only in scale are treated as different values causing unneeded updates

CAY-2660 BigDecimals that differ only in scale are treated as different values causing unneeded updates
…nt values causing unneeded updates

.. PR review .. fixing minor typos
…nt values causing unneeded updates

.. PR review .. fixing minor typos
@andrus
Copy link
Contributor

andrus commented Aug 19, 2020

I just made some minor edits (mostly fixing the typos in type names and javadocs). I don't know if it is possible to add commits to the PR with the Apache setup, so I put it on the new branch:

But a bigger question that I have is whether we need a new injectable service (ValueComparisonStrategy/ValueComparisonStrategyFactory) to handle it. I suspect using ValueObjectType directly should be enough. IIRC we were afraid of a performance impact of having to pass every value through a ValueObjectType . Can we measure it and see if it is of any significance?

@stariy95 stariy95 merged commit 33a6436 into apache:master Sep 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants