Skip to content

Deprecate MongoCustomConversions.BigDecimalRepresentation.STRING #4920

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Open
mp911de opened this issue Mar 11, 2025 · 0 comments · May be fixed by #4957
Open

Deprecate MongoCustomConversions.BigDecimalRepresentation.STRING #4920

mp911de opened this issue Mar 11, 2025 · 0 comments · May be fixed by #4957
Labels
type: enhancement A general enhancement
Milestone
Backlog

Comments

@mp911de
Copy link
Member

mp911de commented Mar 11, 2025

For Spring Data MongoDB 5.0, we should deprecate MongoCustomConversions.BigDecimalRepresentation.STRING (not for removal) and switch the BigDecimal default to BigDecimalRepresentation.DECIMAL128 to indicate that Decimal128 is the preferred data type enabling range queries.

Storing big decimals as string is still a valid option, deprecation expresses that there are certain limitations and applications can use that option if they are aware of the implications.

Follow-up to #3444 and #4916
@mp911de mp911de added the type: enhancement A general enhancement label Mar 11, 2025
@mp911de mp911de added this to the 5.0 M2 (2025.1.0) milestone Mar 11, 2025
@therepanic therepanic linked a pull request Apr 22, 2025 that will close this issue
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
type: enhancement A general enhancement
Projects
None yet
Milestone
Backlog
Development

Successfully merging a pull request may close this issue.

Deprecate MongoCustomConversions.BigDecimalRepresentation.STRING therepanic/spring-data-mongodb
2 participants
@mp911de @christophstrobl