Replies: 2 comments 1 reply
-
That would be the way to go. The issues i would expect is that a lot of the
math logic relies on + - / * and almost everything (including the summary
methods like "sum" and "mean") convert the data to double so there might be
a fair amount of work there.
(I really wish the java maintainers would come out of the 80s and provide
operator overloading.)
…On Mon, Oct 3, 2022 at 4:11 AM hmf ***@***.***> wrote:
Ideally we should handle currency as a BigDecimal. Is their any way one
can "hack" JTablesaw to have such a type column? Could it be as simple as
extending the NumberColumn?
TIA
—
Reply to this email directly, view it on GitHub
<#1154>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2FPASMJQ6LEGYUA2W5O53WBKIL3ANCNFSM6AAAAAAQ3LGFDA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
hmf
-
I did this quite successfully (https://github.com/Alipsa/data-utils/blob/master/src/main/java/tech/tablesaw/api/BigDecimalColumn.java) but i am using it from groovy where there is automatic conversion of operators to the equivalent BigDecimal method. I will check how it behaves in a pure Java environment and submit a PR if positive. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ideally we should handle currency as a
BigDecimal
. Is their any way one can "hack" JTablesaw to have such a type column? Could it be as simple as extending the NumberColumn?TIA
Beta Was this translation helpful? Give feedback.
All reactions