I'm going to be a "small government" candidate. I'll be the government. Just me. No one else.
Tim Holloway wrote:It depends on your datatype in the database AND in the application.
If you define a numeric value in your database as NUMERIC(6,2), then it should always be accurate to 2 decimal places. If you do database calculations on the database server, the standard math rules about precision apply.
However, if you pull values and compute them in a Java application you may have a problem, since there is no "normal" datatype for decimal values except for floating-point, and so if you pull your JDBC/ORM values as float or double, you'll get the standard floating-point fuzz. To get around that, you'd have to either scale the numbers or use a decimal-friendly class like BigDecimal. Which, alas, doesn't have operators, so it's cumbersome to work with.
I'm going to be a "small government" candidate. I'll be the government. Just me. No one else.
Out on HF and heard nobody, but didn't call CQ? Nobody heard you either. 73 de N7GH
Claude Moore wrote:I'm afraid there's no much hope for getting specs. The data are exported 'as are', from a legacy API.
Out on HF and heard nobody, but didn't call CQ? Nobody heard you either. 73 de N7GH
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |