> Ah. In that case, I /would/ argue that this is bad, and that SQLite should > conform to the standard.
That is true, although it is rather unfortunate that the standard makes this statement, IMHO. Unfortunately, this doesn't address the point of whether it should be possible to use NaNs as floating point values, and to store them in tables. As indicated previously, most databases allow it (at least all modern ones seem to), and only SQLite makes a positive effort to handle it as a NULL, introducing (IMHO) strange semantics. I have seen no convincing argument being put up to defend that design choice, so far. Would it be useful to open a ticket on this issue, or will it never be changed e.g. for fear of breaking backward compatibility? In any case, I think it would be useful to spend a paragraph or two in the documentation on the issue of floating point semantics. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
