Re:Microsoft Exchange stops passing mail due to bug on 1/1/22
by bob1029 on Saturday January 01, 2022 @10:54AM
(#29759531)
I have found that any time you would refer to a thing as a "Code" or "Number", you are almost certainly talking about a string. Every property name in our codebase that contains one of these terms is a string type without exception.
[ Parent
| on HN ]
Re:Microsoft Exchange stops passing mail due to bug on 1/1/22
by dannyw on Saturday January 01, 2022 @11:32AM
(#29759955)
If it's not a float or integer, it's a string.
Re:Microsoft Exchange stops passing mail due to bug on 1/1/22
by quesera on Saturday January 01, 2022 @12:25PM
(#29760500)
And if it's currency, it should be an integer not a float.
Re:Microsoft Exchange stops passing mail due to bug on 1/1/22
by bob1029 on Saturday January 01, 2022 @12:36PM
(#29760613)
We use decimals for all currency and rate properties. Integer is fine in many cases too.
Re:Microsoft Exchange stops passing mail due to bug on 1/1/22
by quesera on Saturday January 01, 2022 @01:23PM
(#29761058)
Be careful with floats:
20.40 == (20.39 + 0.01)
=> false
("decimal" can either be colloqually-equivalent to "float", or it can refer to a distinct data type which is supported by some languages and databases. A proper decimal type is currency-safe to use, if available.)