two doubles not equal when they really are
I have a procedure that I am running for three different test cases. For each test case, I pass a string of expected values. The string is split into an array. I am comparing the data in my database ...
Forum Discussion
So I did some troubleshooting. Seems the difference between the test cases that work and the ones that don't are the number of decimal places in the compared values. I mentioned this to my mega geek husband who tells me that this can be the case for values that are defined as type DOUBLE. I don't claim to understand his explanation. But the powers that be who define how computer math works have defined the type double in a way ... .that the values are not equal.
The final upshot is that I don't need the precision of a double. If I case the values as singles, boom, works fine.
I scratch my head. But it works.
The final upshot is that I don't need the precision of a double. If I case the values as singles, boom, works fine.
I scratch my head. But it works.