Regarding: "Yes, but shouldn't I avoid the representation problem..."
I can envision a sign over the entrance to floating point computer numbers
saying,
"ABANDON ALL HOPE OF EQUALITY TESTS, ALL YE WHO ENTER HERE."
I think that even casting a value as floating point means that you're willing
Yes, but shouldn't I avoid the representation
problem if the string I use to build my INSERT command is obtained through
double writtendouble=atof("0.1234567890123456");
stream << "'" << writtendouble << "'" // stream
is a string stream whose precision is set to 30
By doing this way,
Stéphane Thiers
wrote:
If you do:
INSERT INTO myTable
VALUES('0.12345678901234559') // the column is of REAL type
and read back the value
SELECT * FROM myTable
then you get a value==0.12345678901234600 !!
the 2 values are different. What's the problem??
There is an infinite number of str
3 matches
Mail list logo
