-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/03/12 21:48, Simon Slavin wrote: > But it's not what the docs say:
NaN support changed in SQLite 3.5.9 (May 2008): http://www.sqlite.org/changes.html#version_3_5_9 However cvstrac no longer shows code so I couldn't work out if NaN was converted to NULL during calculations, or also stored that way. As someone else pointed out, NaNs and NULLs have very similar properties which is presumably why this approach was chosen. I have no idea what the standard says, but this also appears relevant: sqlite> select typeof(1.0/0); null Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9uqIYACgkQmOOfHg372QQ6PwCgoQjGCemoT4f0G0DAgjmX8Emm Qg4AoLOFttq8FgAel8w618BECp/+jCTx =2z8X -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
