Richard Hipp <d...@sqlite.org> wrote: > In the actual use case that inspired this question (and for which, after > seeing the alternatives, I think I'll stick with SQLite's magical > processing of min()) the mtime value is a floating point number, and we all > know the hazards of comparing floating point numbers for equality, right?
This applies when the floating point number is the result of calculations. If you just read a number twice from the same source, the two copies should compare equal just fine. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
