On 9/9/2015 11:19 AM, Constantine Yannakopoulos wrote: > On Wed, Sep 9, 2015 at 4:54 PM, Igor Tandetnik <igor at tandetnik.org> wrote: > >> A comparison like this would not generally be a proper collation. The >> equivalence relation it induces is not transitive - it's possible to have A >> == B and B == C but A != C (when A is "close enough" to B and B is "close >> enough" to C, but A and C are just far enough from each other). >> > > ?Out of curiosity, doesn't this also apply also to numeric (real number) > comparisons since SQLite3 uses IEEE floating point arithmetic??
What aspect of IEEE floating point arithmetic makes comparisons unsafe, in your opinion? Given two IEEE numbers (NaNs and INFs excepted), the comparison would only ever declare them equal if their representations are bit-for-bit identical; it doesn't play "close enough" games. What again seems to be the problem? -- Igor Tandetnik
